#2438: Authentication of non-ascii user names does not work in TG 2.x
---------------------------------+------------------------------------------
 Reporter:  chrisz               |        Owner:  Gustavo
     Type:  defect               |       Status:  closed 
 Priority:  high                 |    Milestone:  2.1    
Component:  TurboGears           |      Version:  trunk  
 Severity:  major                |   Resolution:  fixed  
 Keywords:  repoze.who identity  |  
---------------------------------+------------------------------------------
Changes (by chrisz):

  * status:  reopened => closed
  * resolution:  => fixed

Comment:

 Thanks a lot for fixing this os quickly, Gustavo.

 Concerning the charset issue: It's true that iso-8859-1 is the http
 default encoding, but only for 'text/...' based MIME types, whereas we're
 dealing with 'application/x-www-form-urlencoded' here. So I'm not sure
 that would be against the specs. Anyway, I have now included 'utf-8' as
 the sa_auth.charset setting for quickstarted TG2 projects so the default
 charset does not really matter.

 This was a big step forward, and I can now log in with a non-ascii user
 name, but there are still some open problems:

  * The repr() of User objects yielded the non-ascii user name which lead
 to various problems. Fixed this already in the TG2 trunk.
  * Error when trying to log in with non-ascii password: #2452
  * Can't log out after logging in with non-ascii user name: #2453

 But these seem to be different issues so I think we can close this ticket
 now.

-- 
Ticket URL: <http://trac.turbogears.org/ticket/2438#comment:14>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development

-- 
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en

Reply via email to