Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <6939922.1150238015710.JavaMail.jira@brutus>
Date: Tue, 13 Jun 2006 22:33:35 +0000 (GMT+00:00)
From: "Emmanuel Lecharny (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Commented: (DIRSERVER-631) Creation of entry with special
 (and escaped) character in RDN leads to wrong attribute value
In-Reply-To: <23633528.1149258929770.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DIRSERVER-631?page=comments#action_12416094 ] 

Emmanuel Lecharny commented on DIRSERVER-631:
---------------------------------------------

This is a really bad problem we have ...

Some explainations on how DN should be treated can be found here : http://docs.safehaus.org/display/APACHEDS/DN+normalization+and+parsing

This is supposed to be done this way, but it's not. The normalizationService does not transform the DN accordingly to the AttributeType.

Changing that will cost time, and tests. 

Unless I'm totally wrong, of course :)


> Creation of entry with special (and escaped) character in RDN leads to wrong attribute value
> --------------------------------------------------------------------------------------------
>
>          Key: DIRSERVER-631
>          URL: http://issues.apache.org/jira/browse/DIRSERVER-631
>      Project: Directory ApacheDS
>         Type: Bug

>     Versions: 1.0-RC3
>  Environment: ApacheDS 1.0 RC 3
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
> Microsoft Windows XP version 5.1 Service Pack 1
>     Reporter: Stefan Zoerner
>  Attachments: AddingEntriesWithSpecialCharactersInRDNTest.java
>
> If one creates an entry with a special character in its RDN value (e.g. #, <, ...) which is escaped in the (R)DN, the resulting entries has the escape char (\) in its attribute value as well. Example:
> Creating this entry:
> dn: cn=Bush\, Kate,dc=example,dc=com
> objectclass: person
> objectclass: top
> sn: Bush
> cn: Bush, Kate
> like this
> $ ldapmodify -h localhost -p 10389 -D "uid=admin,ou=system" -w ****** -a -f KateBush.ldif
> adding new entry cn=Bush\, Kate,dc=example,dc=com
> leads to an entry like that
> $ ldapsearch -h localhost -p 10389 -b "dc=example,dc=com" -s sub "(sn=Bush)"
> version: 1
> dn: cn=Bush\, Kate,dc=example,dc=com
> objectclass: person
> objectclass: top
> sn: Bush
> cn: Bush\, Kate
> The expected for cn is "Bush, Kate", as provided by the LDIF above. The same error occurs with several characters (other than comma). I'll attach a JNDI JUnit test which demonstrates the issue with test methods using different characters (and the test passes on other directory servers).
> Note: This problem may be related to DIRSERVER-628.

-- 
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