Chapter 9. Directory Server RFC support
Find the list of notable supported LDAP-related RFCs. Note that it is not a complete list of RFCs that Directory Server supports.
9.1. LDAPv3 Features
- Technical Specification Road Map (RFC 4510)
- This is a tracking document and does not contain requirements.
- The Protocol (RFC 4511)
Supported with the following exceptions:
- RFC 4511 Section 4.4.1. Notice of Disconnection: Directory Server terminates the connections in this case.
- RFC 4511 Section 4.5.1.3. SearchRequest.derefAliases: LDAP aliases are not supported.
- RFC 4511 Section 4.13. IntermediateResponse Message
- Directory Information Models (RFC 4512)
Supported with the following exceptions:
- RFC 4512 Section 2.4.2. Structural Object Classes: Directory Server supports entries with multiple structural object classes.
- RFC 4512 Section 2.6. Alias Entries
- RFC 4512 Section 4.1.2. Attribute Types: The attribute type COLLECTIVE is not supported.
- RFC 4512 Section 4.1.4. Matching Rule Uses
- RFC 4512 Section 4.1.6. DIT Content Rules
- RFC 4512 Section 4.1.7. DIT Structure Rules and Name Forms
RFC 4512 Section 5.1.1. altServer
Note that RFC 4512 enables LDAP servers to not support the previously listed exceptions. For further details, see RFC 4512 Section 7.1. Server Guidelines.
- Authentication Methods and Security Mechanisms (RFC 4513)
- Supported.
- String Representation of Distinguished Names (RFC 4514)
- Supported.
- String Representation of Search Filters (RFC 4515)
- Supported.
- Uniform Resource Locator (RFC 4516)
- Supported. However, this RFC is mainly focused on LDAP clients.
- Syntaxes and Matching Rules (RFC 4517)
Supported. Exceptions:
-
directoryStringFirstComponentMatch -
integerFirstComponentMatch -
objectIdentifierFirstComponentMatch -
objectIdentifierFirstComponentMatch -
keywordMatch -
wordMatch
-
- Internationalized String Preparation (RFC 4518)
- Supported.
- Schema for User Applications (RFC 4519)
- Supported.
- entryUUID Operational Attribute (RFC 4530)
- Supported.
- Content Synchronization Operation (RFC 4533)
- Supported.
9.2. Authentication methods
- Anonymous SASL Mechanism (RFC 4505)
-
Not supported. Note that RFC 4512 does not require the
ANONYMOUSSASL mechanism. However, Directory Server supports LDAP anonymous binds. - External SASL Mechanism (RFC 4422)
- Supported.
- Plain SASL Mechanism (RFC 4616)
-
Not supported. Note that RFC 4512 does not require the
PLAINSASL mechanism. However, Directory Server supports LDAP anonymous binds. - SecurID SASL Mechanism (RFC 2808)
- Not supported. However if a Cyrus SASL plug-in exists, Directory Server can use it.
- Kerberos V5 (GSSAPI) SASL Mechanism (RFC 4752)
- Supported.
- CRAM-MD5 SASL Mechanism (RFC 2195)
- Supported.
- Digest-MD5 SASL Mechanism (RFC 2831)
- Supported.
- One-time Password SASL Mechanism (RFC 2444)
- Not supported. However if a Cyrus SASL plug-in exists, Directory Server can use it.
9.3. X.509 Certificates schema and attributes support
LDAP Schema Definitions for X.509 Certificates (RFC 4523)
- Attribute types and object classes: Supported.
- Syntaxes: Not supported. Directory Server uses binary and octet syntax.
- Matching rules: Not supported.
