ietf-corpus

rfc-4523

Lightweight Directory Access Protocol (LDAP) Schema Definitions for X.509 Certificates

K. Zeilenga
date2006-06 streamIETF wgnon working group statusPROPOSED STANDARD pages24 canonicalhttps://www.rfc-editor.org/rfc/rfc4523 doi10.17487/RFC4523 errataview
This document describes schema for representing X.509 certificates, X.521 security information, and related elements in directories accessible using the Lightweight Directory Access Protocol (LDAP). The LDAP definitions for these X.509 and X.521 schema elements replace those provided in RFCs 2252 and 2256. [STANDARDS-TRACK]

obsoletes

Extracted elements (24)

design-rationale §2.1

No LDAP-specific encoding is defined for Certificate, CertificateList, CertificatePair, or SupportedAlgorithm syntaxes because these types have changed over time; mandating ;binary transfer preserves the exact signed octets without re-encoding.

ldap, pkix, security

interoperability-note §5.5

The strongAuthenticationUser (OID 2.5.6.15) and certificationAuthority (OID 2.5.6.16) object classes are deprecated in favor of pkiUser and pkiCA respectively; implementations should migrate to the newer classes.

ldap, pkix

normative-requirement §2.1 MUST

As values of Certificate syntax contain digitally signed data, values of this syntax and the form of each value MUST be preserved as presented to protect signature integrity.

ldap, pkix, security

normative-requirement §2.1 SHOULD

Values of Certificate, CertificateList, CertificatePair, and SupportedAlgorithm syntaxes SHOULD be encoded using Distinguished Encoding Rules (DER) per X.690.

ldap, pkix, crypto

protocol-element §3.7

The algorithmIdentifierMatch matching rule (OID 2.5.13.40) compares a presented AlgorithmIdentifier assertion against a SupportedAlgorithm attribute value per X.509 clause 11.3.7.

ldap, pkix, crypto

protocol-element §4.2

The cACertificate attribute type (OID 2.5.4.37) holds X.509 certificates issued to a CA, uses certificateExactMatch for equality, and requires ;binary transfer.

ldap, pkix

protocol-element §3.1

The certificateExactMatch matching rule (OID 2.5.13.34) compares a CertificateExactAssertion against a Certificate attribute value, matching by serial number and issuer as defined in X.509 clause 11.3.1.

ldap, pkix

protocol-element §3.5

The certificateListExactMatch matching rule (OID 2.5.13.38) and certificateListMatch rule (OID 2.5.13.39) match CRL attribute values against assertion values identifying issuer, thisUpdate, and optional distribution point.

ldap, pkix

protocol-element §3.2

The certificateMatch matching rule (OID 2.5.13.35) compares a CertificateAssertion against a Certificate attribute, supporting rich multi-field filtering including validity period, key usage, subject, and policy.

ldap, pkix

protocol-element §4.4

The certificateRevocationList (OID 2.5.4.39), authorityRevocationList (OID 2.5.4.38), and deltaRevocationList (OID 2.5.4.53) attribute types hold CRL values, use certificateListExactMatch, and require ;binary transfer.

ldap, pkix

protocol-element §5.3

The cRLDistributionPoint object class (OID 2.5.6.19) is a STRUCTURAL class that MUST have a cn attribute and MAY hold CRL-related attributes; used to represent CRL distribution point directory entries.

ldap, pkix

protocol-element §5.4

The deltaCRL object class (OID 2.5.6.23) is an AUXILIARY class that MAY hold deltaRevocationList, used to augment entries with delta CRL data.

ldap, pkix

protocol-element §5.2

The pkiCA object class (OID 2.5.6.22) is an AUXILIARY class that MAY hold cACertificate, certificateRevocationList, authorityRevocationList, and crossCertificatePair; it supersedes certificationAuthority and certificationAuthority-V2.

ldap, pkix

protocol-element §5.1

The pkiUser object class (OID 2.5.6.21) is an AUXILIARY class derived from top that MAY contain userCertificate; it supersedes the deprecated strongAuthenticationUser class.

ldap, pkix

protocol-element §4.1

The userCertificate attribute type (OID 2.5.4.36) holds X.509 certificates issued to the user, uses certificateExactMatch for equality, and requires ;binary transfer.

ldap, pkix

registry §7

IANA registered an LDAP Object Identifier for the LDAP X.509 Certificate schema elements introduced in this document, and updated the LDAP Descriptor registry with 22 descriptors (matching rules, attribute types, object classes) mapping to their OIDs.

ldap, pkix, registry

security-consideration §6

Certificate signatures only protect the integrity of the signed content itself; without LDAP data integrity protections (or lower-layer e.g. IPsec), a server cannot verify client requests were unaltered in transit, and clients cannot verify query results. Implementations are recommended to use LDAP authentication and data integrity services (RFC4513, RFC4511).

ldap, pkix, security

wire-format §2.5 MUST

Assertion syntaxes CertificateExactAssertion (OID 1.3.6.1.1.15.1), CertificateAssertion (OID 1.3.6.1.1.15.2), and related assertion types MUST be encoded using Generic String Encoding Rules (GSER) per RFC3641.

ldap, pkix

wire-format §A.1

CertificateExactAssertion GSER encoding is a sequence with mandatory serialNumber (INTEGER) and issuer (rdnSequence Name) fields, used to uniquely identify a certificate for exact matching.

ldap, pkix

wire-format §A.5

CertificateListExactAssertion GSER encoding contains mandatory issuer (Name) and thisUpdate (Time), plus optional distributionPoint (DistributionPointName), used for exact CRL matching.

ldap, pkix

wire-format §2.1

The Certificate syntax (OID 1.3.6.1.4.1.1466.115.121.1.8) carries an X.509 Certificate value. No LDAP-specific encoding is defined; DER encoding is strongly preferred and ;binary transfer is required.

ldap, pkix

wire-format §2.2

The CertificateList syntax (OID 1.3.6.1.4.1.1466.115.121.1.9) carries an X.509 CertificateList (CRL) value. DER encoding preferred, ;binary transfer required.

ldap, pkix

wire-format §2.3

The CertificatePair syntax (OID 1.3.6.1.4.1.1466.115.121.1.10) carries an X.509 CertificatePair value for cross-certification. DER encoding preferred, ;binary transfer required.

ldap, pkix

wire-format §2.4

The SupportedAlgorithm syntax (OID 1.3.6.1.4.1.1466.115.121.1.49) carries an X.509 SupportedAlgorithm value. DER encoding preferred, ;binary transfer required.

ldap, pkix, crypto