Hello Chris -
To do what you describe below, the best way is to enclose your existing AuthBy clauses with an AuthBy GROUP and put the RewriteUsernames there. Note that in the second AuthBy GROUP, you will need to remove what was added in the first AuthBy GROUP.
<Handler Called-Station-Id = /4242$/>
AuthByPolicy ContinueUntilAccept
<AuthBy GROUP>
RewriteUsername s/^/foo#/
<AuthBy LDAP2>
...
</AuthBy>
</AuthBy>
<AuthBy GROUP>
RewriteUsername s/^foo#//
RewriteUsername s/^them#//
RewriteUsername s/$[EMAIL PROTECTED]/
<AuthBy RADIUS>
...
</AuthBy>
</AuthBy>
</Handler>
regards
Hugh
On Friday, Feb 21, 2003, at 08:11 Australia/Melbourne, Chris Fedde wrote:
On Thu, 20 Feb 2003 14:17:15 +1100 Hugh Irvine wrote: +------------------ | Hello Chris - | | If you can recognise the different usernames, you can do this: | +------------------The auth request comes in as, for example, User-Name = cfedde. <Handler Called-Station-Id = /4242$/> AuthByPolicy ContinueUntilAccept <AuthBy LDAP2> ... </AuthBy> <AuthBy RADIUS> ... </AuthBy> </Handler> But for the <AuthBy LDAP2> clause I need RewriteUsername s/^/foo#/ and for the <AuthBy RADIUS> I need RewriteUsername s/^them#// RewriteUsername s/$[EMAIL PROTECTED]/ I'm not sure if I can make your recomendation do that. Am I just overlooking something obvious? Thanks -- chris fedde === 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.
