(RADIATOR) SimultaneousUse using internal session database

[Hugh Irvine]

Hello Dave, Hello Vangelis -

Dave is correct in his comments below.

There are several things to be aware of with session databases in general.

First - the NAS stores the string that was entered by the user in its 
internal table of active connections (usually). This means that you 
need the original string for comparison purposes if you are going to 
query the NAS.

Second - the original internal session database only includes one 
username string and for the reason given above, it is the original 
string.

Third - if you are doing simultaneous use checking between multiple 
copies of Radiator (ie. a primary and a secondary, or multiple 
load-shared servers), you must use an SQL session database so all 
instances of Radiator have the same view of the current online 
population.

Therefore, we give you the option with the SQL session database to 
modify the default schema to include both versions of the username 
string if you wish to, and we also give you to option to supply your 
own session database queries so you can query the NAS with the 
original username string and do your counts on the rewritten username 
string.

hth

Hugh

ps - the format of the internal session database is unlikely to 
change any time soon, although it is on our list ....


At 3:37 PM -0400 6/18/01, Kitabjian, Dave wrote:
>  > P.S. I think it would be very helpful if you included an
>>  option for case
>>  insensitivity for the internal session database in a future
>>  version of RADIATOR
>
>You're on the right track. What it needs to store is two things:
>
>- the ORIGINAL name as coming from the NAS. That will allow us to make sure
>we SNMP get the exact name.
>
>- the REWRITTEN name which should match what is stored in our user database.
>That will allow us to have a single entity to COUNT in the Session DB to
>enforce concurrency limits against.
>
>It would be nice if support for this were part of the standard Radiator
>configs.
>
>Dave
>===
>Archive at http://www.open.com.au/archives/radiator/
>Announcements on radiator-announce at open.com.au
>To unsubscribe, email 'majordomo at open.com.au' with
>'unsubscribe radiator' in the body of the message.

-- 

NB: I am travelling this week, so there may be delays in our correspondence.

Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.