Hello Lisa -
On Tue, 10 Oct 2000, Lisa Goulet wrote:
> Hi Colleagues,
>
> We have a customer who have their own Radiator set up. In addition to our
> authentication they want to "check" certain attributes. This means that the
> authentication responsibility is split between the two radiator servers.
>
> Does this make sense? If so, how can this be accomplished? I don't know the
> details yet but need to find out if it is at all possible.
>
Yes, very simple.
# configure local AuthBy
<AuthBy ....>
Identifier LocalCheck
.....
</AuthBy>
# configure remote Radiator
<AuthBy RADIUS>
Identifier RemoteCheck
Host ....
Secret .....
.....
</AuthBy>
# configure customer Realm (or Handler)
<Realm customer.nl>
AuthByPolicy ContinueWhileAccept
AuthBy LocalCheck
AuthBy RemoteCheck
....
</Realm>
Note that the RemoteCheck must come last (AuthBy RADIUS forks and does not
return).
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.
