On Tue, 25 May 1999, tom minchin wrote:
> > 1. Radiator expects User-Password = "string", but the legacy file has
> > entries in the format Password = "string". Or is this just a matter of
> > making a dictionary entry like:
> >
>
> vi legacy-users
> :1,$s/Password/User-Password/g
>
> >
> > 2. Some (OK, lots) of the "strings"s are "UNIX" - meaning that the
> > radiusd should use system routines to verify the username and supplied
> > password against the system passwd/shadow password file. I can't see a
> > reference to doing this with Radiator.
> >
>
> vi legacy-users
> :1,$s/User-Password = "UNIX"/Auth-Type = System/g
True, but as the legacy-users file is not static, I was hoping to avoid
this kind of kludge.
Having said that, your comment (plus a good night's sleep ;-) has given me
an idea: <AuthBy FILE> by default "will only reread the user database when
the files modification time changes". It should be possible to do the
above traslations while reading the user database, hopefully without
incurring an "unacceptable" performance hit.
Generalising this, it would be "nice" to have a hook for a translator
function to be called to implement arbitrary translations. Mike?
Thanks for the other hints related to this.
Regards,
Neale.
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
