[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         | horde at dbservice.com
 Summary            | LDAP entry failes when cn contains comma
 Queue              | Turba
 Version            | HEAD
 Type               | Bug
 State              | Feedback
 Priority           | 1. Low
 Owners             | 
-----------------------------------------------------------------------


horde at dbservice.com (2006-10-18 15:11) wrote:

Yes and no.
1.  Comma in common name seems to work now for me
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?