(RADIATOR) RewriteUsername help
Hugh Irvine
hugh at open.com.au
Wed Feb 2 23:36:11 CST 2005
Hello Steve -
Its much easier to understand your questions if you include a copy of
the configuration file and a trace 4 showing what is happening.
You should have a look at section 6.2 in the Radiator 3.11 reference
manual ("doc/ref.html") to see what special characters are available
for use in queries. In your case you might find %w to be useful?
Can you explain exactly what you are wanting to do?
regards
Hugh
On 2 Feb 2005, at 20:30, Steve Shippa wrote:
> Right, that would add '@realm', however is there any way to add the
> "defaultrealm" which is different for each customer
> (cust001.example.com, cust002.example.com, cust00n.example.com) as I'm
> doing authentication with the same <Handler>
>
> Thanks,
> -Steve
>
> Mark O'Leary wrote:
>
>> I think the following would add "@realm" to the end of 'plain'
>> usernames:
>>
>> RewriteUsername s/^([^@]+)$/$1\@realm/
>>
>> M.
>>
>> --
>> Mark O'Leary, ITO (Networks)
>> Communications, Manchester Computing
>> mark at manchester.ac.uk
>>
>>
>>
>>> -----Original Message-----
>>> From: owner-radiator at open.com.au [mailto:owner-radiator at open.com.au]
>>> On Behalf Of Steve Shippa
>>> Sent: 02 February 2005 13:39
>>> To: radiator at open.com.au
>>> Subject: (RADIATOR) RewriteUsername help
>>>
>>> Can anyone tell me if it's possible (and if so, help with the regexp
>>> as I'm not too good at them) to use a RewriteUsername parameter to
>>> add the defaultrealm (i.e. cust001.example.com) to the username
>>> (i.e. steve)?
>>>
>>> I store usernames in my db as user at cust001.example.com,
>>> user at cust002.example.com, etc. My customers log into specific
>>> clients where I apply the defaultdomain of custXXX.example.com and
>>> while I see places in the log where user at custXXX.example.com is
>>> showing up, when the query to the db happens, it uses the NAS
>>> 'User-Name' and not user at custXXX.example.com
>>> (User-Name+defaultrealm). The log shows:
>>>
>>> Tue Feb 1 15:26:34 2005: DEBUG: Query is: 'select PASS_WORD,
>>> STATICADDRESS, TIMELEFT, MAXLOGINS, SERVICENAME, BADLOGINS,
>>> VALIDFROM, VALIDTO from RADUSERS where USERNAME='steve'':
>>> Tue Feb 1 15:26:34 2005: DEBUG: Radius::AuthRADMIN looks for match
>>> with steve Tue Feb 1 15:26:34 2005: DEBUG: AuthBy RADMIN result:
>>> REJECT, No such user Tue Feb 1 15:26:34 2005: INFO: Access rejected
>>> for steve No such user
>>>
>>> Any ideas?
>>>
>>> Thanks,
>>> -Steve
>>>
>>>
>>>
>>> --
>>> Archive at http://www.open.com.au/archives/radiator/
>>> Announcements on radiator-announce at open.com.au To unsubscribe, email
>>> 'majordomo at open.com.au' with 'unsubscribe radiator' in the body of
>>> the message.
>>>
>>> --
>>> No virus found in this incoming message.
>>> Checked by AVG Anti-Virus.
>>> Version: 7.0.300 / Virus Database: 265.8.2 - Release Date: 28/01/2005
>>>
>>>
>>
>>
>
> --
> Archive at http://www.open.com.au/archives/radiator/
> Announcements on radiator-announce at open.com.au
> To unsubscribe, email 'majordomo at open.com.au' with
> 'unsubscribe radiator' in the body of the message.
>
>
NB:
Have you read the reference manual ("doc/ref.html")?
Have you searched the mailing list archive
(www.open.com.au/archives/radiator)?
Have you had a quick look on Google (www.google.com)?
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, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
-
CATool: Private Certificate Authority for Unix and Unix-like systems.
--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.
More information about the radiator
mailing list