On Wed, 20 Oct 2004, EROS wrote:
Well, the pb is that if you are doing this a user could login for more
than 90days after his first connection.
And this kind of user already have a max session timeout in setting.
So now I make a perl script that check every 24h the first connection of
a user and set the Expiration attribute to 90day more.
But I feel that it is not a correct solution... If you have some best
Use the postauth section. If you are using sql for user database it's just a
question of creating a proper INSERT query which will set the Expiration
attribute on the first logon. If you don't use sql (but ldap etc) you can do it
with a perl script, again on first logon. Hope this helps.
...
thx
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] De la part de Alan
DeKok
Envoy? : mercredi 20 octobre 2004 18:16
? : [EMAIL PROTECTED]
Objet : Re: Expiration counter
EROS [EMAIL PROTECTED] wrote:
For example, a user could connect 90d after his first connection and
no more. I don't know how to setup a counter like this , if somebody
has an idea !
rlm_counter. See raddb/radiusd.conf for examples.
You should say reset = never, and then set the maximum session time
to 3600*24*90.
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
--
Kostas Kalevras Network Operations Center
[EMAIL PROTECTED] National Technical University of Athens, Greece
Work Phone: +30 210 7721861
'Go back to the shadow' Gandalf
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
