This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note

Page References

Incoming links Outgoing links
RootDSE
RootDSE

Version management

Difference between version and

At line 1 added 45 lines
!!! Overview
[Root Directory Server Agent Service Entry] or [{$pagename}] is defined in [RFC 2251] Section 3.4:\\
An LDAP server [MUST] provide information about itself and other information that is specific to each server. This is represented as a group of attributes located in the rootDSE ([DSA-Specific Entry]), which is named with the zero-length LDAPDN. These attributes are retrievable if a client performs a base object search of the root with filter (objectClass=*)", however they are subject to access control restrictions. The [{$pagename}] [MUST NOT] be included if the client performs a subtree search starting from the root.
!! Also Known As
* [DSA-Specific Entry] ([DSE])
* [Root Directory Server Agent Service Entry]
[DSAs] may allow [DUAs] to modify these attributes.[{$pagename}] is primarily a [Discovery Mechanism] for [Lightweight Directory Access Protocol]
!! [{$pagename}] Contents
The following attributes of the root DSE are defined in section 5 of 5. Additional attributes may be defined in other documents. Servers MUST recognize these attribute names, but it is not required that a server provide values for these attributes, when the attribute corresponds to a feature which the server does not implement.
* [namingContexts]
* [subschemaSubentry]
* [altServer]
* [supportedExtension] - ([LDAP Extensions and Controls Listing])
* [supportedControl] - ([LDAP Extensions and Controls Listing])
* [supportedSASLMechanisms]
* [supportedLDAPVersion]
* [supportedFeatures] - ([LDAP Extensions and Controls Listing])
* [supportedAuthPasswordSchemes]
* [supportedGroupingTypes]
* [vendorName]
* [vendorVersion]
* [dsaName]
* [changelog]
* [firstChangeNumber]
* [lastChangeNumber]
If the server does not master entries and does not know the locations of schema information, the [subschemaSubentry] attribute is not present in the root DSE. If the server masters directory entries under one or more schema rules, there may be any number of values of the [subschemaSubentry] attribute in the root [DSE].
!! Issues with [{$pagename}]
Determining whether the server supports any specific [SupportedControl], [SupportedExtension] or [SupportedFeatures] presents some problems because, even though directory servers should publish the OIDs for supported features in the [SupportedFeatures] attribute in the [{$pagename}], as an example, [RFC 4525] merely states that servers should publish the OID of the Modify-Increment extension in the root DSE, not that servers must publish the OID.[1]
!! [RootDSE Example]
* Information on [Retrieving RootDSE]
!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
----
* [#1] - [http://ldapmaven.com/2011/08/02/mastering-modify-increment/|http://ldapmaven.com/2011/08/02/mastering-modify-increment/|target='_blank'] - based on informayion retreived 2013-06-15
This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthorTop