| Summary | IDN Bug: Unable to log in with IDN domain, only with a punycode domain it is possible to log in |
| Queue | Horde Framework Packages |
| Queue Version | Git master |
| Type | Bug |
| State | Not A Bug |
| Priority | 2. Medium |
| Owners | |
| Requester | torben (at) dannhauer (dot) info |
| Created | 03/14/2013 (4577 days ago) |
| Due | |
| Updated | 03/14/2013 (4577 days ago) |
| Assigned | |
| Resolved | 03/14/2013 (4577 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
domains before it passes the credentials forward to authentication?
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.
domains before it passes the credentials forward to authentication?
State ⇒ Not A Bug
authentication backend. Login credentials with non-ascii characters
don't work in a portable way, because there almost zero authentication
schemes which have knowledge of charsets.
Priority ⇒ 2. Medium
Patch ⇒ No
Milestone ⇒
Queue ⇒ Horde Framework Packages
Summary ⇒ IDN Bug: Unable to log in with IDN domain, only with a punycode domain it is possible to log in
Type ⇒ Bug
State ⇒ Unconfirmed
To log into horde the punycode variant of the domain has to be used.
It is not possible to log in with the IDN version which would be very
comfortable for users having IDN domains.
Once logged into horde, the punycode emailadress is correctly parsed
and displayed as IDN version of the eMailadress. (displayed in the
upper right corner)
Is there any hidden switch available to force horde to punify IDN
domains before it passes the credentials forward to authentication?
Thanks,
Torben