Re: Expiration attribute limitation - max year?
Marinko Tarlac wrote: > Hello I'm working on something and I can figure what is the max year for > expiration attribute? It's a 32-bit Unix timestamp, in seconds since 1970. 2039 *is* the maximum. > Here is the problem > > rlm_sql: Failed to create the pair: failed to parse time string > "December 31 2039 00:00:00" > > When I enter December 31 2035 00:00:00 as a year it works but 2039 > doesn't. Is there any way to avoid this limit? No. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Expiration attribute
Thanks Ivan Best regards Message: 3 Date: Thu, 22 Nov 2007 07:51:41 +0100 From: <[EMAIL PROTECTED]> Subject: Re: Expire attribute To: "FreeRadius users mailing list" Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-2 Attribute name is Expiration. It is a check item so it does go into radcheck. I use is == as operator, but := should work as well. Format that works for me is: November 28 2007 20:26:43 Ivan Kalik Kalik Informatika ISP - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: expiration attribute as an offset?
Very nice, thank you Alan. On 1/28/07, Alan DeKok <[EMAIL PROTECTED]> wrote: liran tal wrote: > > Interesting. > I actually wouldn't want to go into involving scripts Well, then you won't implement a solution, I guess. > but this gets me > curious - what would be the way to > run a script on the first login? This is something freeradius related, > isn't it? Uh... yes. See the docs for how to run scripts. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: expiration attribute as an offset?
liran tal wrote: > > Interesting. > I actually wouldn't want to go into involving scripts Well, then you won't implement a solution, I guess. > but this gets me > curious - what would be the way to > run a script on the first login? This is something freeradius related, > isn't it? Uh... yes. See the docs for how to run scripts. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: expiration attribute as an offset?
Interesting. I actually wouldn't want to go into involving scripts but this gets me curious - what would be the way to run a script on the first login? This is something freeradius related, isn't it? Thanks. On 1/23/07, Alan DeKok <[EMAIL PROTECTED]> wrote: liran tal wrote: > Is it possible to set the expiration attribute to be of an offset type? No. Because something has to remember when the offset started. > Say I set an offset of +30 days, and the user logins for the first time > only 6 months from now. So once he > login'ed once then the counter will start counting 30 days from his > first login and then expire the account. Run a script on the first login that updates the DB with the proper expiration. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: expiration attribute as an offset?
liran tal wrote: > Is it possible to set the expiration attribute to be of an offset type? No. Because something has to remember when the offset started. > Say I set an offset of +30 days, and the user logins for the first time > only 6 months from now. So once he > login'ed once then the counter will start counting 30 days from his > first login and then expire the account. Run a script on the first login that updates the DB with the proper expiration. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: expiration attribute
It is easy for with my method. I suposse that you have RADIUS counts with a specific login, if you want that a count expires in 30 days after its activation, you only have to get the activation date (you know with NOW() in mysql) and add to this date 30 in MySQL sentences. This calculated date is save in the radcheck table in the field ExpitationDate. Santiago "Milver S. Nisay" <[EMAIL PROTECTED]> wrote: > The next challenge for a prepaid dialup would be , is there a possibility > that an > account's expiration would be modified, using MsSQL queries inside > sqlcounter.conf, on the first successful authentication I would suggest running an external program to do that. > For Ex. An prepaid dialup card is to expire within 30 days starting May 1, > but the user who bought it used the prepaid dialup account on the May 29, is > there an attribute that will modify or prolong the expiration for 29 days > more since it was used successfully on the 29th day of the month, therefore > activating the dialup account on the first successful usage. That is a *very* specialized requirement, and is not possible with the default modules. You should be able to write a simple shell script to catch that case, and update the database. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html _ Protege tu correo del spam y los virus con MSN 8. Prueba gratis dos meses MSN 8. http://join.msn.com/?pgmarket=es-es&XAPID=199&DI=1055 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: expiration attribute
"Milver S. Nisay" <[EMAIL PROTECTED]> wrote: > The next challenge for a prepaid dialup would be , is there a possibility > that an > account's expiration would be modified, using MsSQL queries inside > sqlcounter.conf, on the first successful authentication I would suggest running an external program to do that. > For Ex. An prepaid dialup card is to expire within 30 days starting May 1, > but the user who bought it used the prepaid dialup account on the May 29, is > there an attribute that will modify or prolong the expiration for 29 days > more since it was used successfully on the 29th day of the month, therefore > activating the dialup account on the first successful usage. That is a *very* specialized requirement, and is not possible with the default modules. You should be able to write a simple shell script to catch that case, and update the database. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: expiration attribute
Thanks Alan. My expiration attribute is now working To add more details, the OP field must be set to "==" and not ":=" and it worked smoothly. The next challenge for a prepaid dialup would be , is there a possibility that an account's expiration would be modified, using MsSQL queries inside sqlcounter.conf, on the first successful authentication For Ex. An prepaid dialup card is to expire within 30 days starting May 1, but the user who bought it used the prepaid dialup account on the May 29, is there an attribute that will modify or prolong the expiration for 29 days more since it was used successfully on the 29th day of the month, therefore activating the dialup account on the first successful usage. I hope I made my point clear here. Anyone? - Original Message - From: "Alan DeKok" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, April 20, 2004 3:41 PM Subject: Re: expiration attribute > "Milver S. Nisay" <[EMAIL PROTECTED]> wrote: > > i have inserted expiration attribute with radcheck table, with a PAP account > > as shown below > > | 243 | milver | Expiration | := | 20040419153024 | > > That isn't a date. It's simply a long number. > > > but if i manipulate the expiration attribute to a date which has expired or > > past already, > > authentication STILL seems to go, nothing changed, the account can still > > logon with freeradius. > > No, you edit the Expiration to have another value, which still isn't > a date. > > In the 0.9.3 release, try "01 Jan 2004". In the CVS snapshots, you > can use HH:MM:SS, too. > > Alan DeKok. > > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html > > - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: expiration attribute
"Milver S. Nisay" <[EMAIL PROTECTED]> wrote: > i have inserted expiration attribute with radcheck table, with a PAP account > as shown below > | 243 | milver | Expiration | := | 20040419153024 | That isn't a date. It's simply a long number. > but if i manipulate the expiration attribute to a date which has expired or > past already, > authentication STILL seems to go, nothing changed, the account can still > logon with freeradius. No, you edit the Expiration to have another value, which still isn't a date. In the 0.9.3 release, try "01 Jan 2004". In the CVS snapshots, you can use HH:MM:SS, too. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: expiration attribute
Hi, The expiration attribute is the account expiration date. The account will be disabled on that date."Milver S. Nisay" <[EMAIL PROTECTED]> wrote: can anyone elaborate more of the "Expiration" attribute?is it an attribute of password age or expiration for password?i am am trying to play around for an expiration attribute -- expiration foran accountfrom MySQL table and not from system accounts, using freeradius under FC1.anyone?//milver- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.htmlJulius IguguSouthWork Co. Ltd.234 (802) 320-7540 Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢
