[Tickets #2940] LDAP entry fails when CN contains comma or multiple spaces

[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 fails when CN contains comma or multiple spaces
 Queue              | Turba
 Version            | HEAD
 Type               | Bug
 State              | Feedback
 Priority           | 1. Low
 Owners             | 
-----------------------------------------------------------------------


horde at dbservice.com (2006-10-19 01:09) wrote:

> First of all, if composite attributes aren't working for you, please 
> open a new ticket with a full description
It's a problem in developer release, the stable release is OK. That is why
I didnt open any bug here. 

> So how _should_ we handle this?
Do not handle it, the behaviour is OK, I was wrong, it's LDAP feature to
ignore spaces when manipulating the entry. The same for case sensitivity.
ALICE BOB => error adding contact, exists.

I think this bug can be closed.