directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleks M (JIRA)" <>
Subject [jira] [Commented] (DIRSTUDIO-935) Reading root DSE
Date Thu, 11 Jul 2013 19:09:48 GMT


Aleks M commented on DIRSTUDIO-935:

It seems that eDirectory now requires that you specify that you want to read operational attributes
when reading the root DSE, it's no longer enough with just *, now you also need the +.
If I add SchemaConstants.ALL_OPERATIONAL_ATTRIBUTES to the following code in
then it works:

// load all user attributes
        search = new Search( null, browserConnection, Dn.EMPTY_DN, ISearch.FILTER_TRUE, new
            { SchemaConstants.ALL_USER_ATTRIBUTES, SchemaConstants.ALL_OPERATIONAL_ATTRIBUTES
}, SearchScope.OBJECT, 0, 0,
            Connection.AliasDereferencingMethod.NEVER, Connection.ReferralHandlingMethod.IGNORE,
false, null );

Is this a change you can make to Studio?
I guess it's OK according to the RFC4512:

"It is noted that root DSE
   attributes are operational and, like other operational attributes,
   are not returned in search requests unless requested by name."

> Reading root DSE
> ----------------
>                 Key: DIRSTUDIO-935
>                 URL:
>             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:

View raw message