LDAP: Accessing Operational Information CNS 4650 Fall 2004 Rev. 2

Server Information Allows developer/admin to not have to make assumptions about directory Often termed the “root object” or root DSE (p.174) Server is required to recognize the the attributes Server is NOT required to have the attributes or values in those attributes

Root DSE attributes altServer Other servers that can be contacted if this server is unavailable namingContexts List of naming contexts held by the LDAP server supportedControl List of the OIDs of controls the LDAP server supports supportedExtension List of the OIDs of the extensions the LDAP server supports

Root DSE attributes supportedLDAPVersion Lists LDAP version supported supportedSASLMechanisms Lists the SASL mechanisms supported by the LDAP server Can also have custom (vendor specific) attributes supportedFeature (OpenLDAP)

OpenLDAP Controls From the ldap.h file: /* LDAP Controls */ #define LDAP_CONTROL_MANAGEDSAIT" " #define LDAP_CONTROL_NOOP" " #define LDAP_CONTROL_SORTREQUEST " " #define LDAP_CONTROL_SORTRESPONSE" " #define LDAP_CONTROL_VLVREQUEST " " #define LDAP_CONTROL_VLVRESPONSE " " #define LDAP_CONTROL_VALUESRETURNFILTER " "

OpenLDAP Extensions From the ldap.h file: #define LDAP_EXOP_START_TLS" " #define LDAP_EXOP_MODIFY_PASSWD" " #define LDAP_TAG_EXOP_MODIFY_PASSWD_ID((ber_tag_t) 0x80U) #define LDAP_TAG_EXOP_MODIFY_PASSWD_OLD((ber_tag_t) 0x81U) #define LDAP_TAG_EXOP_MODIFY_PASSWD_NEW((ber_tag_t) 0x82U) #define LDAP_TAG_EXOP_MODIFY_PASSWD_GEN((ber_tag_t) 0x80U) #define LDAP_EXOP_X_WHO_AM_I" "

How to Query for Operational Information Set the search base to “” Set scope to “base” Set the search filter to: ‘(objectclass=*)’ Query for certain attributes: namingContexts Query for all attributes “+” (RFC 3673)

Example Query ldapsearch -h b "" -s base -x -W '(objectclass=*)' "+"

Subschema Contains the schema definitions No standard place That is what the operational attributes are used for! Query the root DSE for “subschemasubentry” OpenLDAP - cn=Subschema eDirectory/Active Directory - cn=schema

Subschema The subschema contains all objectclasses and attributes the server supports Developer/Admin could query and search for objectclass or attribute Example: inetOrgPerson

Subschema Search Objectclasses ldapsearch -h b "cn=Subschema" -s base -x -W '(objectclass=*)' attributetypes Attributes ldapsearch -h b "cn=Subschema" -s base -x -W '(objectclass=*)' attributetypes Combination of Both ldapsearch -h b "cn=Subschema" -s base -x -W '(objectclass=*)' objectclassses attributetypes

Subschema Search Matching Rules ldapsearch -h b "cn=Subschema" -s base -x -W '(objectclass=*)' matchingRules LDAP Syntaxes ldapsearch -h b "cn=Subschema" -s base -x -W '(objectclass=*)' ldapSyntaxes Ask for it all ldapsearch -h b "cn=Subschema" -s base -x -W '(objectclass=*)' subschema

Monitor Used to store other server information in the entry Server version (not LDAP but release) Total connections Startup time Bytes sent Information different from root DSE This entry is more on the running condition, network information, etc.

Monitor Usually can be queried by: Base = “cn=Monitor” Scope = “base” Filter = ‘(objectclass=*)’ But DN can differ from server to server Best to query root DSE and return “monitor” For OpenLDAP it must be specified at compile time