Creation of an entry with multivalued RDN leads to wrong DN in search results.

• Key: DIRSERVER-703
• Type: Bug
• Status: Closed
• Resolution: Fixed
• Priority: Major
• Assignee: Emmanuel Lecharny
• Reporter: Stefan Zoerner
• Affects Version/s: 1.0-RC4

Environment

* ApacheDS 1.0 RC4 SNAPSHOT
* Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
* Windows XP Professional SP2

Description

I use Apache Directoty Server 1.0 RC4 SNAPSHOT with server.xml unchanged. If I create an entry with multivalued RDN like this:

dn: cn=Kate Bush+sn=Bush,dc=example,dc=com
objectclass: top
objectclass: person
sn: Bush
cn: Kate Bush

i.e.
$ ldapmodify -D "uid=admin,ou=system" -w ****** -a -f multiValued.ldif
adding new entry cn=Kate Bush+sn=Bush,dc=example,dc=com
$

the entry is returned in searches with a wrong dn:

$ ldapsearch -D "uid=admin,ou=system" -w ****** -b "dc=example,dc=com" -s one "(sn=Bush)"
version: 1
dn: cn=Kate Bush,dc=example,dc=com
objectclass: person
objectclass: top
sn: Bush
cn: Kate Bush
$ ldapsearch -D "uid=admin,ou=system" -w ****** -b "cn=Kate Bush+sn=Bush,dc=example,dc=com" -s base "(sn=Bush)"
version: 1
dn: cn=Kate Bush,dc=example,dc=com
objectclass: person
objectclass: top
sn: Bush
cn: Kate Bush
$

The expected dn is cn=Kate Bush+sn=Bush,dc=example,dc=com in both cases.
I'll attach a JUnit test which demonstrates this issue soon.

Comments

[Stefan Zoerner]

This issues dealed with the creation of entries with multivalued RDNs as well.

[Stefan Zoerner]

JUnit testcase to demonstrate this issue. It uses JNDI. Note that only the test case testMultiValuedRdnName fails with Apache DS. I have checked this test with the following servers:
    * OpenLDAP 2.3
    * Sun Java System Directory Server 5.2
    * IBM Tivoli Directory Server 6.0
For these three servers, it passes completely.

[Alex Karasulu]

This looks like an LDAP DN issue. It happens after an add all to the LDAP dn. Here's a test that shows how this is broken:

    /**
     * Test to see if a DN with multiRdn values is preserved after an addAll.
     */
    public void testAddAllWithMultivaluedAttribute() throws InvalidNameException
    {
        LdapDN dn = new LdapDN( "cn=Kate Bush+sn=Bush,ou=system" );
        LdapDN target = new LdapDN();
        target.addAll( target.size(), dn );
        assertEquals( "cn=Kate Bush+sn=Bush,ou=system", target.toString() );
        assertEquals( "cn=Kate Bush+sn=Bush,ou=system", target.getUpName() );
    }

Trying to fix this now.

[Alex Karasulu]

I've isolated the problem to the upName calculation in the RdnParser for an Rdn. Here are some unit tests that show the problem exactly.

[Alex Karasulu]

This is way over my head right now. Having a hard time understanding this code. I'll wait for Emmanuel to come back and fix this one.

[Alex Karasulu]

Emmanuel this is a patch which adds Stefan's tests to the SVN repository in 1.0 branch. Once you fix this issue please apply this patch here and to 1.1 trunks. If you want me to do it just assign me the issue after fixing the Rdn problem I can confirm the integration tests.

[Emmanuel Lecharny]

Fixed in revision 431163 & 431164 for 1.0 and 1.1 branches.

This was a stupid mistake... (does anybody have heard about intelligent mistakes ? ;), upName was computed before the loop which parse the others atavs.

[Alex Karasulu]

Emmanuel did you apply the patch that adds Stefan's tests? If not want me to apply them?

[Stefan Zoerner]

I can confirm that the test case attached to this issue works fine now with Apache DS 1.0 RC 4. Therefore I close the issue.