Task #3629
Handle CILogon DN containing UTF-7 encoded special characters
100%
Description
After going back and forth with CILogon about how to handle subject DNs with special characters (remember they are using CN=givenName surname) they decided to encode using UTF-7 which gives encoded strings like:
CN=+aQVbUA-,O=Google,C=US,DC=cilogon,DC=org
for
CN=椅子,O=Google,C=US,DC=cilogon,DC=org
This includes Spanish, French , Portuguese characters as well. We just need to decode these correctly when using them and displaying them.
Subtasks
Related issues
History
#1 Updated by Ben Leinfelder over 11 years ago
I'm now trying to convince CILogon to use UTF-8 escapes like this:
CN=\u6905\u5b50,O=Google,C=US,DC=cilogon,DC=org
#2 Updated by Ben Leinfelder over 11 years ago
At this point in the discussion, it sounds like we are sticking with UTF-7 escape sequences in the DN and we will not be decoding them into the character representations they were based on. Using RFC2253 for representing the DN as a string gives us:
CN=+aQVbUA-,O=Google,C=US,DC=cilogon,DC=org
NOTE the backslash escaping for the + sign.
#3 Updated by Matthew Jones over 11 years ago
Note that, given that DNs are potentially extremely cryptic, we need to eliminate them from user interfaces, in favor of using a real common name and possibly email addrress to display user identities, or maybe by using an EPPN.
#4 Updated by Ben Leinfelder about 11 years ago
- Status changed from New to Closed
- translation missing: en.field_remaining_hours set to 0.0
