Hello Jason -
You should use multiple AuthBy clauses, like this:
# define Realms or Handlers
<Handler ....>
AuthByPolicy ContinueUntilAccept
<AuthBy LDAP2>
.....
</AuthBy>
<AuthBy SQL>
.....
</AuthBy>
.....
</Handler>
And you can use the AuthLog clause to log authentication successes and/or failures.
regards
Hugh
On Thursday, Nov 7, 2002, at 10:37 Canada/Eastern, Jason Signalness wrote:
Hello,NB: I am travelling this week, so there may be delays in our correspondence.
I'm working to set up a new Radius server. Essentially, we want it to behave like this:
1) Check our LDAP directory
2) Check out Oracle db
3) If there are problems reaching either database, let someone know.
From what I've heard, it's not possible to tell the difference (with Radiator) between failed logins (bad passwords, invalid users, etc) and database problems (such as an unreachable LDAP directory).
Is this true? If not, how can one go about detecting these failures in an AuthBy or Handler clause?
Thanks,
--
Jason Signalness, Systems Administrator
Basin Telecommunications, Inc.
--
===
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.
--
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.
