[Tickets #2940] LDAP entry failes 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
 Queue              | Turba
 Version            | HEAD
 Type               | Bug
 State              | Feedback
 Priority           | 1. Low
 Owners             | 
-----------------------------------------------------------------------


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

> 2.  Multiple spaces are still replaced with one space.
>
>     cn=John<space><space>Doe
>
>     is saved into backend as
>
>     cn=John<space>Doe
>
> IMO cn is like a primary key here. Why do we manipulate it before 
> saving in the  backend?

Not sure what you mean - if the name is edited, then CN has to change
since that's the name element. And really the DN should be the primary
key, not CN, right?

Anyway, do you know where the space is diappearing?