Hello AL -
Radiator looks for an exact match of the username, followed by DEFAULT, DEFAULT1, DEFAULT2 and so on. This allows you to perform complex authentication with DEFAULT* users that cascade through to other authentication methods. If you only want to match on the exact username you can disable the DEFAULT* lookups by specifying NoDefault in the AuthBy clause.
<AuthBy ...>
.....
NoDefault
.....
</AuthBy>regards
Hugh
On Thursday, Jul 31, 2003, at 17:52 Australia/Melbourne, Charles Alexander McCain wrote:
I was wondering how come sometimes a user will pass through as DEFAULT and
sometimes will pass as DEFAULT2 , DEFAULT3, DEFAULT4 etc.
What is the reason for this ?
How come all my users can't pass through as DEFAULT ?
Thanks, AL
=== 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.
NB: have you included a copy of your configuration file (no secrets), together with a trace 4 debug showing what is happening?
-- 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.
