[Tickets #12115] Re: IDN Bug: Unable to log in with IDN domain, only with a punycode domain it is possible to log in

[noreply at bugs.horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: http://bugs.horde.org/ticket/12115
------------------------------------------------------------------------------
  Ticket           | 12115
  Aktualisiert Von | torben at dannhauer.info
  Zusammenfassung  | IDN Bug: Unable to log in with IDN domain, only with a
                   | punycode domain it is possible to log in
  Warteschlange    | Horde Framework Packages
  Version          | Git master
  Typ              | Bug
  Status           | Not A Bug
  Priorität        | 2. Medium
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


torben at dannhauer.info (2013-03-14 12:49) hat geschrieben:

>> Is there any hidden switch available to force horde to punify IDN
>> domains before it passes the credentials forward to authentication?
>
> A preauthenticate hook?

Ah, a hook would be a solution! I missed that point, sorry.

I'm using the SQL backend.
Since my user table is also used by Postfix, and Postfix requires the  
punycode notation of the IDN domains, I have to store it in that way  
in the table.

Once logged in, horde encoded the name correctly to display it in IDN  
version without any configuration - so I hope I can autodetect IDN  
logins and convert them into punicode as horde does it to display the  
user email address.

thanks.