2014-09-04 - Re: [GRASE-Hotspot] implementing activation from first login

Header Data

From: Mohammad Javad <pe***t@gmail.com>
Message Hash: a55ee7117b48b876f495c27eae564c53a4176895bd5fc3f32068f493464ae8a0
Message ID: <CAL7r4-X+-CfdoGLn5d3pv7Lrw52+bmegSNLEMmJBEF30z9Jdqw@mail.gmail.com>
Reply To: <CAESLx0JkNaen0FQceWQQHqmWzhi8LdpA_sxP5Zm=rOPCYahEEQ@mail.gmail.com>
UTC Datetime: 2014-09-04 23:31:11 UTC
Raw Date: Fri, 05 Sep 2014 11:01:11 +0430

Raw message 

Hi Tim thanks for your great support. I'm looking forward to see this
feature. I was somehow able to get it to work. Let me explain how. We have
written a windows application(accounting system) to keep track of the
vouchers we give out. I looked at the radius database and i found that
there is an attribute called "Expiration". I played with this attribute and
i found out this is the value i need too implement this feature. In our
windows application (C# .net) when i give out a voucher, i register the
voucher and customer information in another database and then it sets the
expiration date in the radcheck table. It seems to be working but i was
wondering, is it a good solution? Does it interfere with anything?( i mean
the cron jobs you mentioned). I wish i could do this in the login page code
to save some hassle. So that when a user tries to login for the first time,
the right expiration date can be set based on the type of voucher. But i
don't know much php. For my use, i don't realty need the reporting feature.
Maybe there is an in-code solution for me you could suggest?

There's one other thing i need to ask you. I think i read that your
software has a feature that automatically removes expired vouchers
periodically. Am i right? What's the period? For my use i need to keep
expired vouchers at least 3 months after expiration. Then  it's OK to be
removed. Can it be done?

Can you also give me an example of how to customize the login portal for
the stable version? I've read all the topics related to this matter but I
wasn't able to figure it out and web designing isn't really my thing but i
can understand it. I know it can be done through the radmin portal but I'm
afraid to touch anything. :-)

Sorry to bother you with all my questions.
Thanks Tim
On Sep 5, 2014 4:17 AM, "Timothy White" <ti***8@gmail.com> wrote:

> Hi Mohammad
>
> In theory, this is easy to implement. In practice, getting it right is
> harder. It's something I'm hoping I can get implemented well in the near
> future. It's fairly "easy" to implement if all vouchers expire within a
> month of first, usage, however, due to how we "compact" the accounting data
> each month, it's harder for longer expiries. I'm hoping for a 2 pronged
> approach, where at first login we can get the correct expiry dynamically,
> but a script will run regularly and update the dynamic expiry to a static
> one so it can span more than a month.
>
> Tim
>
>
> On Sun, Aug 31, 2014 at 5:50 PM, Mohammad Javad Ra'adi <
> pe***t@gmail.com> wrote:
>
>> Hello Tim and the community. I've been wondering how it is possible to
>> implement voucher activation from first login. Currently you can only
>> specify expiration date and the voucher will be expired as soon as it
>> reaches expiration date whether the voucher is used or not. Is our possible
>> to set the expiration date upon first login?
>> I've read this post
>> https://groups.google.com/a/grasehotspot.org/forum/m/#!topic/grase-hotspot/zfZfFZZFyfA)
>> but i don't understand how freeradius  and I'm unclear about the concepts.
>> I've been reading about freeradius for the past 3 days and i still can't
>> figure out how you've managed to implement the attributes and counters. If
>> you could guide me or show me a source to better understand the whole thing
>> it would be amazing.
>> Thanks everyone
>>
>> --
>> This mailing list is for the Grase Hotspot Project
>> http://grasehotspot.org
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Grase Hotspot" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to gr***e@grasehotspot.org.
>> To post to this group, send email to gr***t@grasehotspot.org.
>> Visit this group at
>> http://groups.google.com/a/grasehotspot.org/group/grase-hotspot/.
>> To view this discussion on the web visit
>> https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/f48b8276-15f7-4463-932c-a1ccc65a0f2a%40grasehotspot.org
>> .
>>
>
>  --
> This mailing list is for the Grase Hotspot Project http://grasehotspot.org
> ---
> You received this message because you are subscribed to the Google Groups
> "Grase Hotspot" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to gr***e@grasehotspot.org.
> To post to this group, send email to gr***t@grasehotspot.org.
> Visit this group at
> http://groups.google.com/a/grasehotspot.org/group/grase-hotspot/.
> To view this discussion on the web visit
> https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/CAESLx0JkNaen0FQceWQQHqmWzhi8LdpA_sxP5Zm%3DrOPCYahEEQ%40mail.gmail.com
> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/CAESLx0JkNaen0FQceWQQHqmWzhi8LdpA_sxP5Zm%3DrOPCYahEEQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

Thread