directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Endi S. Dewata (JIRA)" <>
Subject [jira] Updated: (DIREVE-245) Add operation with capital letters in the suffix failed.
Date Wed, 07 Sep 2005 20:39:30 GMT
     [ ]

Endi S. Dewata updated DIREVE-245:


Attached is a test case that exposes the problem.

In (line 87), the code tries to check the parent entry before adding.
However, it uses the user-provided DN instead of the normalized one.

        Name parentDn = new LdapName( upName );
        parentDn = parentDn.getSuffix( 1 );

        // check if we don't have the parent to add to
        assertHasEntry( nextInterceptor, "Attempt to add under non-existant parent: ", parentDn

Fixing this will solve the add operation problem, but we should check other operations too.

> Add operation with capital letters in the suffix failed.
> --------------------------------------------------------
>          Key: DIREVE-245
>          URL:
>      Project: Directory Server
>         Type: Bug
>   Components: server main
>     Versions: 0.9.3
>     Reporter: Endi S. Dewata
>     Assignee: Alex Karasulu
>  Attachments:
> Set up a partition with dc=Apache,dc=Org as the suffix. Run the server then add the following
> dn: ou=users,dc=Apache,dc=Org
> objectClass: organizationalUnit
> ou: users
> The operation will fail with a return code of 32 (no such object).
> When an add operation is issued, the server calls the DefaultContextPartitionNexus.hasEntry()
which in turn calls DefaultContextPartitionNexus.getBackend(). The current getBackend() implementation
requires that the DN parameter has to be normalized. However, the DN parameter coming from
hasEntry() is not normalized, causing it to fail finding the appropriate backend. So, either
the getBackend() has to be modified to normalize the parameter, or all callers have to be
checked to make sure they normalize the parameter first.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message