[ http://issues.apache.org/jira/browse/DIRSERVER-756?page=all ]
Emmanuel Lecharny reopened DIRSERVER-756: ----------------------------------------- Assignee: Emmanuel Lecharny Bloody hell !!! You are right Endi... The search result entry requests does not return the correct DN, because it use the internal representation (byte[]) instead of using the user provided value, which contains escaped values. Here, we have two options : 1) work with the internal value, but escape all the special chars 2) work with the stored UP value. I think the bnest solution is (2), because the UP value is supposed to be valid - it has successfully been parsed when the first request arrived -. This will impact two parts : - searchResultEntry - all the response that contains a LdapResult and which returns a MatchedDN. I already have a fix for the first request, but the question is : which version will integrate this modification ? any suggestion ? > Problem with escaped comma in DN > -------------------------------- > > Key: DIRSERVER-756 > URL: http://issues.apache.org/jira/browse/DIRSERVER-756 > Project: Directory ApacheDS > Issue Type: Bug > Affects Versions: pre-1.0, 1.0-RC4 > Reporter: Endi S. Dewata > Assigned To: Emmanuel Lecharny > > 1. Add the following entry: > ldapadd -h localhost -p 10389 -D uid=admin,ou=system -w secret -x > dn: cn=Dewata\, Endi,ou=Users,ou=system > objectClass: person > cn: Dewata, Endi > sn: Dewata > 2. Search the entry: > ldapsearch -h localhost -p 10389 -D uid=admin,ou=system -w secret -x -b > "ou=system" > # > dn: cn=Dewata, Endi,ou=Users,ou=system > objectclass: person > objectclass: top > sn: Dewata > cn: Dewata, Endi > The escape character (\) is missing from the DN, causing it to become invalid. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira