Hello David -
On Thu, 06 Jul 2000, David Lloyd wrote:
> I am going to implement a backup for if our SQL server fails, but this has
> to work on the first try. So I'm running it by you folks just to be sure.
>
To be safe, I strongly suggest you set up a test rig and make sure it works the
way you expect it to before putting anything into service.
> If my SQL server is down I want to authenticate from a file that is
> updated once a day.
>
> So my config file would read like this:
>
> <AuthBy SQL>
> Identifier SQLAuth
> ...
> </AuthBy>
>
> <AuthBy FILE>
> Identifier BackupAuth
> ...
> </AuthBy>
>
> <Hander ....>
> ...
> AuthByPolicy ContinueWhileIgnore
> AuthBy SQLAuth
> AuthBy BackupAuth
> ...
> </Handler>
>
> Am I forgetting anything? Also, if I *don't* specify Nocache in my AuthBy
> FILE, when is the user file read? Is it before or after the StartupHook
> is executed?
>
The above should work, however you should be careful with your timeout values,
as the AuthBy SQL timeout defaults to 60 seconds, which is almost guaranteed to
exceed the dialler timeouts on most PC's. It won't do you any good going to a
backup authentication method if the customer has already hung up.
In an AuthBy FILE, the user file is read initially at startup, and is reread
whenever the modification time on the file changes. I would not recommend using
the NoCache parameter, as it will have a very large performance hit.
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.
