[
https://issues.apache.org/jira/browse/DIRSERVER-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kiran Ayyagari resolved DIRSERVER-1860.
---------------------------------------
Resolution: Fixed
Assignee: Kiran Ayyagari
This was fixed with the commit http://svn.apache.org/r1527280.
> Invalid DN in returned entry
> ----------------------------
>
> Key: DIRSERVER-1860
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1860
> 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 http://sourceforge.net/p/ldap-sdk/discussion/1001257/thread/ffbae6dd/
>
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
