Thanks Hugh,
It works exactly as desired.
For reference I used <Handler
Realm=/foo.com.au$/> and it works correctly.
I opted against using <Handler
Username=/foo.com.au$/> as some users log in without a realm and the
(default realm) client clause adds it for them.
Thanks again,
Brian Morris
----- Original Message -----
Sent: Monday, July 21, 2003 6:44 PM
Subject: Re: (RADIATOR) Wildcards in
Handler Clause
Hello Brian -
You can do something like
this:
<Handler User-Name =
/foo.com.au$/> .... </Handler>
BTW - as always you
should test thoroughly to verify correct
operation.
regards
Hugh
On Monday, Jul 21, 2003, at
18:14 Australia/Melbourne, Brian Morris wrote:
Hi All,/smaller>/fontfamily> Is
it possible to have wildcards in
handlers?/smaller>/fontfamily> I
would like to have a situation where a handler 'handles' everything for a
particular domain level regardles of its subdomains./smaller>/fontfamily> For
example.../smaller>/fontfamily> <Handler
realm=*foo.com.au>/smaller>/fontfamily> This
would handle actions for [EMAIL PROTECTED]/color> as well
as [EMAIL PROTECTED]/color> or
[EMAIL PROTECTED]/color>/smaller>/fontfamily> Is
such a thing possible? or is there another way apart from explicitly
defining every possible realm?/smaller>/fontfamily> Cheers,
Brian Morris/smaller>/fontfamily>
NB:
have you included a copy of your configuration file (no secrets), together
with a trace 4 debug showing what is happening?
-- 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.
|