directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre-Arnaud Marcelot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRSTUDIO-730) LDAP browsing show a dn (an organizational unit) that is not there
Date Mon, 15 Oct 2012 16:08:03 GMT

    [ https://issues.apache.org/jira/browse/DIRSTUDIO-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476234#comment-13476234
] 

Pierre-Arnaud Marcelot commented on DIRSTUDIO-730:
--------------------------------------------------

Do you have any screenshot and LDIF export of that entry?
An LDIF export of the Root DSE might also help.

Thanks!
                
> LDAP browsing show a dn (an organizational unit) that is not there
> ------------------------------------------------------------------
>
>                 Key: DIRSTUDIO-730
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-730
>             Project: Directory Studio
>          Issue Type: Bug
>          Components: studio-apacheds
>    Affects Versions: 1.5.3
>         Environment: Windows Vista SP2, Apache Directory studio Version: 1.5.3.v20100330,
penrose virtual directory server 2.0 and 2.0.1
>            Reporter: Frank IJskes
>
> In the LDAP Browser:
> expand an organizational unit shows the same organizational unit which can be expanded
recursively and infinitely.
> Context:
> I am using penrose virtual directory to convert an ldap to use the "uid" as dn, instead
of using the "cn" as dn.
> When using ldapsearch to search the ldap directory, i do not see this "dc" object.
> When using the softerra ldapbowser, i do not see this object.
> Conclusion: apache directory studio shows me something that is not there.
> This happens ONLY in this container. Other containers do not have this issue. 
> This container is special, because there is a mapping done in the ldap browser that shows
the uid as dn instead of the cn.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message