directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kiran Ayyagari (JIRA)" <>
Subject [jira] [Resolved] (DIRSERVER-1860) Invalid DN in returned entry
Date Sat, 22 Feb 2014 15:18:20 GMT


Kiran Ayyagari resolved DIRSERVER-1860.

    Resolution: Fixed
      Assignee: Kiran Ayyagari

This was fixed with the commit

> Invalid DN in returned entry
> ----------------------------
>                 Key: DIRSERVER-1860
>                 URL:
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: ldap
>    Affects Versions: 2.0.0-M11
>         Environment: Windows Server 2008 R2 Standard
>            Reporter: Charlie Barnett
>            Assignee: Kiran Ayyagari
>            Priority: Minor
>             Fix For: 2.0.0-M11
> I am trying to match entries in two directories and produce an xml file of differences.
ApacheDS is the server for both directories. JXplorer is being used to modify one of the directories.
The modified directory is read using a SearchResultListener. In one case the dn of the SearchResultEntry
passed to the listener is incorrect. It only contains the rdn of the entry. The specific case
is when a new uniqueMember is added to an existing entry of type groupOfUniqueNames. This
occurs with both JXplorer and also with Apache Directory Studio. After starting and stopping
the server the correct dn is contained in the entry passed. Waiting aproximately 15 minutes
also clears the problem. Am using unboundid ldap client library
> Reported problem initially to unboundid but determined by running a proxy that the invalid
dn was being returned from server. Link to unboundui report is

This message was sent by Atlassian JIRA

View raw message