Hello Andrew -
At 7:22 +1100 4/12/00, Andrew Pollock wrote:
><snip>
>
>> 2. define multiple AuthBy clauses
>>
>> <AuthBy SQL>
>> Identifier CheckSQL1
>> DBSource ....
>> DBUsername ....
>> DBAuth ....
>> .....
>> </AuthBy>
>>
>> <AuthBy SQL>
>> Identifier CheckSQL2
>> DBSource ....
>> DBUsername ....
>> DBAuth ....
>> .....
>> </AuthBy>
>>
>> <Realm ....>
>> AuthByPolicy ContinueUntilAccept
>> AuthBy CheckSQL1
>> AuthBy CheckSQL2
>> </Realm>
>>
>
>Correct me if I'm wrong, but won't this mean that CheckSQL2 will be called
>if CheckSQL1 returns an Access-Reject?
Yes. The AuthByPolicy must match the requirement. The above will
continue until it gets an Accept (or falls off the end).
regards
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.
