Hugh Irvine wrote:
>
> Hello Matthias -
>
> On Tue, 10 Oct 2000, Matthias Fechner (Temp) wrote:
> > Hi,
> >
> > i want to integrate a complete fallback, if the database isn't working like
> > client-auth, user-auth or accounting radiator should be use flatfiles. If
> > accounting cannot be write to mysqldb it is written to a
> > flatfile(AcctLogFileName ).
> >
> > I think for the user I only write
> > <Realm bla>
> > <AuthBy SQL>
> > DBSource dbi:mysql:cndps
> > DBUsername radiator
> > DBAuth *****
> > AuthSelect SELECT password,NULL,replyattr FROM snapshot
> > WHERE \
> > loginname='%U' AND realmname='%R'
> >
> > NoDefault
> > # You may want to tailor these for your ACCOUNTING table
> > # You can add your own columns to store whatever you like
> > AccountingStopsOnly
> > AccountingTable accounting
> > AcctColumnDef username,User-Name
> > ........
> > AcctColumnDef disconnect_cause,Ascend-Disconnect-Cause
> > </AuthBy>
> >
> > # use this for fallback
> > <AuthBy FILE>
> > Filename users
> > </AuthBy>
> >
> > AcctLogFileName accounting.log
> > PasswordLogFileName password.log
> > </Realm>
> >
>
> You will need to add an AuthByPolicy to the above:
>
> <Realm bla>
> AuthByPolicy ContinueUntilAccept
> .....
Sorry to reply to such an old message, but shouldn't the AuthByPolicy
here be ContinueWhileIgnore? Otherwise it seems all failed
authentications will unnecessarily go through the flatfile as well.
Viraj.
===
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.
