(RADIATOR) Configuration Questions?

2001-04-03 Thread James Laszko

I was wondering if someone could point me in the right direction


We're trying to setup Radiator to authenticate users that have no realm
or the @tfb.com realm.  Our database is a Platypus SQL database and
we're using the EMERALD auth function.

If the user exists in the database as user, we want him to be able to
authenticate as user or [EMAIL PROTECTED]

If the user exists in the database as user, we want him to be able to
authenticate as [EMAIL PROTECTED] or user


I seem to be missing something, because I can't figure it out..


Also, we're interested in keeping some of our legacy Lucent RADIUS
servers online for authentication.  We would like to throw
authentication requests to the Lucent RADIUS servers from Radiator, but
still do the accounting in our Platypus SQL database.  Any pointers on
this?



Thank you,



James Laszko
TFBnet
[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.



Re: (RADIATOR) Configuration Questions?

2001-04-03 Thread Hugh Irvine


Hello James -

At 21:09 -0700 01/4/3, James Laszko wrote:
I was wondering if someone could point me in the right direction


We're trying to setup Radiator to authenticate users that have no realm
or the @tfb.com realm.  Our database is a Platypus SQL database and
we're using the EMERALD auth function.


OK.


If the user exists in the database as user, we want him to be able to
authenticate as user or [EMAIL PROTECTED]

If the user exists in the database as user, we want him to be able to
authenticate as [EMAIL PROTECTED] or user


I seem to be missing something, because I can't figure it out..


You just need a RewriteUsername to strip the realm (see below).



Also, we're interested in keeping some of our legacy Lucent RADIUS
servers online for authentication.  We would like to throw
authentication requests to the Lucent RADIUS servers from Radiator, but
still do the accounting in our Platypus SQL database.  Any pointers on
this?

Very easy to do - here are some pointers:

# configure AuthBy clauses

AuthBy EMERALD
Identifier CheckEMERALD
DBSource 
DBUsername 
DBAuth 
..
/AuthBy

AuthBy RADIUS
Identifier CheckLUCENT
Host 
Secret 

/AuthBy

# configure Handlers

# accounting requests go here
Handler Request-Type = Accounting-Request
AuthBy CheckEMERALD
/Handler

# authentication requests to LUCENT go here
# configure the Handler appropriately
Handler ..
AuthBy CheckLUCENT
/Handler

# everything else goes here
Handler
# Strip realm
 RewriteUsername s/^([^@]+).*/$1/
AuthBy CheckEMERALD
/Handler


hth

Hugh

-- 

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.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.