Hello Dan -
I would suggest a single session database, but with an additional "SERVICE" column, together with you own queries defined to check it. Have a look at section 6.7 in the Radiator 3.4 reference manual.
regards
Hugh
On Thursday, Dec 5, 2002, at 11:02 Australia/Melbourne, Dan Melomedman wrote:
Hi. Our Radiator needs to authenticate more that one service from the same
realm. We need to guarantee that a user can get one session per each
service with the same account, but only one session. For example, once a
user has authenticated for dial-up, he wants to use a VPN client - one
more session, but for a different service. The trick is a user must not
be allowed to get more than one session for either service. What needs
to be done? A separate session DB for each handler? Anything else?
Thanks.
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
-- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence.
=== Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
