directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Seelmann (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRSTUDIO-935) Reading root DSE
Date Thu, 11 Jul 2013 20:37:48 GMT

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

Stefan Seelmann commented on DIRSTUDIO-935:
-------------------------------------------

Just five lines before there is a second search which requests some well-known operational
attributes and "+". The result of those both searches is merged into the displayed entry.
The reason why we request some specific attributes (namingContexts, supportedControl, etc.)
but also "+" is that not all servers support the RFC3673 "All operational attributes" feature.

So we do two searches:
1.) with attributes: namingContexts subschemaSubentry supportedLDAPVersion supportedSASLMechanisms
supportedExtension supportedControl supportedFeatures vendorName vendorVersion + objectClass
2.) with attributes: *

I wondered why this is done and while browsing through the SVN history I found issue DIRSTUDIO-269.
This was introduces to workaround bad behaviour of BEA Weblogic embedded LDAP, it didn't return
all user attributes if "*" was requested with another attributes.

Now it seems the latest eDirectory server has a similar problem, that it doesn't return all
operational attributes if "+" is requested together with other operational attributes? Can
you verify that by doing a search with an attribute and +, e.g. "namingContexts +"?



                
> Reading root DSE
> ----------------
>
>                 Key: DIRSTUDIO-935
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-935
>             Project: Directory Studio
>          Issue Type: Bug
>    Affects Versions: 2.0.0-M8 (2.0.0.v20130628)
>         Environment: Windows 8 64-bit, Java 7
>            Reporter: Aleks M
>
> Hello
> How can I troubleshoot this issue.
> When connected to an older version of eDirectory and when clicking on the Root DSE I
can see all the attributes available on the Root DSE.
> When I connect to a newer version, in my case 887, Studio displays just the following:
> namingContexts, subschemaEntry, supportedControl, supportedExtension, supportedFeatures,
supportedLDAPVersion, supportedSASLMechanisms, vendorName, vendorVersion.
> Reading the root DSE using another others LDAP tools works fine.
> Which Java class performs the reading of the root DSE?

--
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