[Tickets #2940] LDAP entry fails when cn contains comma

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://dev.horde.org/horde/whups/ticket/?id=2940
-----------------------------------------------------------------------
 Ticket             | 2940
 Updated By         | Chuck Hagenbuch <chuck at horde.org>
-Summary            | LDAP entry failes when cn contains comma
+Summary            | LDAP entry fails when cn contains comma
 Queue              | Turba
 Version            | HEAD
 Type               | Bug
 State              | Feedback
 Priority           | 1. Low
 Owners             | 
-----------------------------------------------------------------------


Chuck Hagenbuch <chuck at horde.org> (2006-10-18 18:26) wrote:

First of all, if composite attributes aren't working for you, please open a
new ticket with a full description. I can't quite follow what you're
talking about, and they are definitely not related to this bug.

Second, if I try to change a CN on my LDAP server to contain multiple
spaces, I get an error. I can't save it to the backend (nothing is
stripped) because the LDAP server thinks they're the same (old DN is
cn=Alice Bob, new DN is quoted by Horde as cn="Alice  Bob" because of the
multiple spaces).

So how _should_ we handle this?