RE: Problem with character Ä in username/password

[Velusamy, Vinodh]

Alan,
Thanks for your response. I am using the radius server to authenticate a web-application using browser usernam/password authentication. Here is the debug info when trying to authenticate an ordinary user Vinodh/vinodh which works perfectly!! :

Waking up in 4 seconds...
--- Walking the entire request list ---
Cleaning up request 7 ID 99 with timestamp 44e57654
Nothing to do.  Sleeping until we see a request.
rad_recv: Access-Request packet from host 10.0.203.118:1026, id=97, length=72
        User-Name = "Vinodh"
        User-Password = "vinodh"
        Service-Type = Authenticate-Only
        NAS-Identifier = "10.0.203.118"
        NAS-IP-Address = 10.0.203.118
  Processing the authorize section of radiusd.conf
modcall: entering group authorize for request 8
  modcall[authorize]: module "preprocess" returns ok for request 8
  modcall[authorize]: module "mschap" returns noop for request 8
    rlm_realm: No '@' in User-Name = "Vinodh", looking up realm NULL
    rlm_realm: No such realm "NULL"
  modcall[authorize]: module "suffix" returns noop for request 8
  rlm_eap: No EAP-Message, not doing EAP
  modcall[authorize]: module "eap" returns noop for request 8
    users: Matched entry DEFAULT at line 152
  modcall[authorize]: module "files" returns ok for request 8
modcall: leaving group authorize (returns ok) for request 8
  rad_check_password:  Found Auth-Type System
auth: type "System"
  Processing the authenticate section of radiusd.conf
modcall: entering group authenticate for request 8
  modcall[authenticate]: module "unix" returns ok for request 8
modcall: leaving group authenticate (returns ok) for request 8
Sending Access-Accept of id 97 to 10.0.203.118 port 1026
Finished request 8
Going to the next request
--- Walking the entire request list ---
Waking up in 6 seconds...
--- Walking the entire request list ---
Cleaning up request 8 ID 97 with timestamp 44e57662
Nothing to do.  Sleeping until we see a request.


I have a setup in FreeRADIUS 0.5 where éâäåçêëèïîìÄæôòû/éâäåçêëèïîìÄæôòû seems to work. I am quite sure it is probably some configuration issue, but am not able to figure out where the issue is. Any help to resolve this is appreciated.

Thanks.

V~


---
Vinodh Velusamy
Software Engineer

Ubizen - a Cybertrust company
Ubicenter, Philipssite 5, 3001 Leuven, Belgium
T: +32 16 28 73 14
F: +32 16 28 71 00 
E-mail: vinodh.velusamy at ubizen.com

www.ubizen.com  - www.cybertrust.com

-----Original Message-----
From: freeradius-users-bounces+vinodh.velusamy=ubizen.com at lists.freeradius.org [mailto:freeradius-users-bounces+vinodh.velusamy=ubizen.com at lists.freeradius.org] On Behalf Of Alan DeKok
Sent: Thursday, August 17, 2006 7:26 PM
To: FreeRadius users mailing list
Subject: Re: Problem with character Ä in username/password

"Velusamy, Vinodh" <vinodh.velusamy at ubizen.com> wrote:
> There seems to be a problem if the username/password contain the character Ä, when trying to authenticate via freeradius.

  No, go back and read the output again:

> rad_recv: Access-Request packet from host 127.0.0.1:33292, id=245, length=98
>         User-Name = "\303\251\303\242\303\244\303\245\303\247\303\252\303\250\303\257\303\256\303\254\303\204\303\246\303\264\303\262\303\273"
>         User-Password = "\222\023S~\345v\322\250\207\216\261\206\242J\301\301\251\006\233\026N\374\014\213\036c\022'\220\r\370\210"

  That's the real contents of the packet.  The '?' is printed simply because it replaces a non-ASCII character.

  Are you sending the server UTF-8 strings in the User-Name?  What client are you using?

  Alan DeKok.
--
  http://deployingradius.com       - The web site of the book
  http://deployingradius.com/blog/ - The blog
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html