01-09-2009 09:38 AM
01-15-2009 11:25 AM
Thanks for the response Craig. I had spoken to the JTAC about this too and must admit that I am more than a little disappointed that this capability has not been built into the software by now.
01-22-2009 05:48 AM - edited 01-22-2009 06:42 AM
It's not a Radius job to set package or account expiry, it's database. When user supplies his authentication data to the server either directly by answering the terminal server's login/password prompts, or using PAP or CHAP protocols. The server obtains the user's personal data from one of the following places:
System Database (The user's login and password are stored in /etc/passwd on the server)
Internal Database (The user's login ID, password etc. are stored in the internal radius database)
SQL authentication (User's details are stored in an SQL database. The database structure is fully determined by the system administrator, Radius does not restrict it in any way. See Interaction with SQL Servers.)
Hopefully it should be clear now that in any case you have to update database fields to set the account expiry.