ldapv3.pdf 7947KB Apr 17 2013 11:30:42 AM - mirror omadata

subSchema
One of the most useful bits of information provided by the
rootDSE is the DN of the subschema object:
subschemaSubentry: cn=subschema
The subSchema object contains the operational schema of the
server, allowing applications to download this information, or
users to investigate the attributes and objects supported by the
DSA without having access to the actual configuration files.
A small part of an example subSchema object:
attributeTypes: ( 1.3.6.1.4.1.6921.2.22 NAME 'morrisondesc' DESC 'RFC1274: use
r identifier' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTA
X 1.3.6.1.4.1.1466.115.121.1.15{256} )
objectClasses: ( 2.5.20.1 NAME 'subschema' DESC 'RFC2252: controlling subschem
a' AUXILIARY MAY ( dITStructureRules $ nameForms $ ditContentRules $ objectCl
asses $ attributeTypes $ matchingRules $ matchingRuleUse ) )
objectClasses: ( 2.5.6.0 NAME 'top' ABSTRACT MUST objectClass )
The OpenLDAP command used to retrieve the subSchema object: ldapsearch -x -b 'cn=subschema' -s base '(objectclass=*)' '+'