Ahh, I see. Sorry I didn't think of that.
Would I be correct in assessing this AuthBy GROUP as behaving sort of like a
quasi-Handler? It seems that it offers some Handler-like control...
Thanks!
Dave
:)
> -----Original Message-----
> From: Hugh Irvine [mailto:[EMAIL PROTECTED]]
> Sent: Friday, January 01, 1904 5:31 AM
> To: Kitabjian, Dave; '[EMAIL PROTECTED]'
> Cc: Wild, Andrew
> Subject: Re: (RADIATOR) RewriteUsername in <AuthBy> ?
>
>
>
> Hello Dave -
>
> The way to do this is with AuthBy GROUP(s):
>
...
>
> Hugh
>
>
> At 16:56 -0500 01/3/27, Kitabjian, Dave wrote:
> >Subject says it all.
> >
> >The docs say you can specify RewriteUsername Globally, in
> Client clauses,
> >and in Realms. (It might be worth mentioning that it appears
> to work in
> >non-realm Handlers, too.)
> >
> >But anyway...
> >
> >I'm wondering if it can work in <AuthBy> clauses?
> >
> >The reason we'd like that is as follows. We do a
> RewriteUsername to strip
> >out garbled characters before passing requests onto LDAP,
> since it will hang
> >LDAP (and sometimes Radiator :-( ). We don't know which
> Clients will end up
> >using the AuthBy LDAP, and the requests may arrive via other
> Handlers, too.
> >So the logical place to put it is in the AuthBy. Otherwise,
> we'll have to
> >make sure to specify it in each Handler, which is less than elegant.
> >
> >Does this make sense?
> >
> >Thanks!
> >
> >Dave
> >NetCarrier
===
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.
