Hello Dean -
On Tue, 24 Oct 2000, Dean Brandt wrote:
> Hi Hugh,
>
> This sort of works but if a user is not listed in the
> /etc/raddb/users file then the request is rejected. I want the process to
> be conditional that the user is in Platypus, and only add the check/treply
> attributes to users who ARE listed in the users file, if the user is not
> listed then they have already got past Platypus, let them connect. Can
> this be done?
>
Sure - like this:
# configure AuthBy PLATYPUS and AuthBy FILE
<AuthBy PLATYPUS>
Identifier CheckPlatypus
DBSource dbi:Sybase:DSN
DBUsername xxxxxxx
DBAuth xxxxxxx
</AuthBy>
<AuthBy FILE>
Identifier CheckUsers
Filename /etc/raddb/users
</AuthBy>
# configure Realm
<Realm DEFAULT>
AuthBy CheckUsers
</Realm>
The file /etc/raddb/users would contain this:
# file /etc/raddb/users
DEFAULT Auth-Type = CheckPlatypus
someuser Auth-Type = CheckPlatypus
.......
anotheruser Auth-Type = CheckPlatypus
......
.......
hth
Hugh
--
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.
