Hello Erwin -
On Wed, 11 Oct 2000, Erwin Wortel wrote:
>
> Hi,
>
> We are using Radiator (2.16.1) for a short time now. For user authentication we
> are
> making use of an LDAP server. For backup reasons we have a secondary (backup)
> ldap server. I've implemented this in Radiator as described below.
>
> Now I am experiencing the following problem :
>
> When a user not exists in de LDAP DB or a wrong password has been sent then
> Radiator tries the secondary LDAP server (as I told him to do so [AuthByPolicy
> ContinueUntilAccept] :-) And ofcourse, this doesn't give an 'access accept'
> either.
>
> But, I'd like the secondary LDAP server only be contacted if the primary LDAP
> server doesn't give any response at all.
>
> My question is as follows :
>
> Am I making a mistake in the implementation, and if so, what is the right one
> :-)
> or is it not possible to do it 'my way'.
>
It is not clear how you are using the AuthBy LDAP clauses (I asume they are
being called from the AuthBy FILE's?). Perhaps if you gave me a bit more detail
on exactly what you want to do, I'll be able to give you some suggestions.
regards
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.
