Argh.. this is where everyone should yell at me to RTFM! Just stumbled
over the Identifier parameter for SessionDatabase clauses... just shoot
me :)
Jeremy
On Wed, Apr 18, 2001 at 11:22:54AM +1000, Jeremy Burton wrote:
Hi All,
I have a question 'bout session databases... We have a setup where we
provide dialup access for a subsidiary (but separate) company - ie they
have their own customers but use our dialup equipment. To do this, we give
them their own dialin number on our NAS and use
Handler Client-Port-DNIS=9xxx as the way of telling radiator to
forward the requests onto their radius server. That way, a user of their
service doesn't need to append @theirname.com.au to the end of their
usernames to get authenticated properly. This is all working fine except
for one problem: we use an SQL session database to keep track of
simultaneous use for our own customers. If a user called user1 logs into
their service, and then a user called user1 with simultaneous use=1 logs
into our service, they are denied. Why? Because the session database
already has an entry for user user1. In theory, a nice way around it would
be to have in the session database username@realm, however that is just
the problem: we don't have differenct realms here. Is there some way of
indicating within an AuthBy that we don't want the session database used
for the present AuthBy. This way, if we have an AuthBy purely for
forwarding, we can bypass the session database.
Thanks,
Jeremy
--
Jeremy Burton
Database Administrator, Netspace Online Systems
[EMAIL PROTECTED]
[EMAIL PROTECTED]
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
--
Jeremy Burton
Database Administrator, Netspace Online Systems
[EMAIL PROTECTED]
[EMAIL PROTECTED]
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
