Hello Cliff -
This is very easy to configure - something like this:
# define AuthBy clauses
<AuthBy SQL>
Identifier CheckSQL
.....
</AuthBy>
<AuthBy RADIUS>
Identifier CheckAnotherRadiusServer
.....
</AuthBy>
# define Realms or Handlers
<Handler ...>
AuthByPolicy ContinueUntilAccept
AuthBy CheckSQL
AuthBy CheckAnotherRadiusServer
</Handler>
Have a look at section 6.27 in the Radiator 2.18.2 reference manual.
hth
Hugh
On Wednesday 15 August 2001 00:22, Cliff Cole wrote:
> Hello,
> I have sort of a strange situation that I have not ever thought about
> that we would like to do here at my company. We are wanting to have a
> realm check a database (or flat file if need be) and if the username is not
> in the database it then passes the username@realm on to another radius
> server for authentication. If the user is not in our databse when it
> passes through to the other Radius server it also will set global
> attributes for the users that get authenticated with the second radius. I
> really do not know where to start this configuration, so any help is very
> appreciated.
>
> Thanks,
> Cliff
>
> ===
> 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.
