52 entries

Matching rules

Matching rules tell the server how to compare values for a syntax: equality, ordering, and substring.

OIDNameDefined in
2.5.13.40algorithmIdentifierMatchRFC 4523
1.2.36.79672281.1.13.6allComponentsMatchRFC 3687
2.5.13.16bitStringMatchRFC 4517
2.5.13.13booleanMatchRFC 4517
1.3.6.1.4.1.1466.109.114.1caseExactIA5MatchRFC 4517
2.5.13.5caseExactMatch Equality that respects case. Far rarer than caseIgnoreMatch, because most human-facing text wants case folded away; you …RFC 4517
2.5.13.6caseExactOrderingMatchRFC 4517
2.5.13.7caseExactSubstringsMatchRFC 4517
1.3.6.1.4.1.1466.109.114.2caseIgnoreIA5MatchRFC 4517
1.3.6.1.4.1.1466.109.114.3caseIgnoreIA5SubstringsMatchRFC 4517
2.5.13.11caseIgnoreListMatchRFC 4517
2.5.13.12caseIgnoreListSubstringsMatchRFC 4517
2.5.13.2caseIgnoreMatch The default equality rule for Directory String attributes, and the reason Smith and smith compare equal. It also folds …RFC 4517
2.5.13.3caseIgnoreOrderingMatchRFC 4517
2.5.13.4caseIgnoreSubstringsMatchRFC 4517
2.5.13.34certificateExactMatchRFC 4523
2.5.13.38certificateListExactMatchRFC 4523
2.5.13.39certificateListMatchRFC 4523
2.5.13.35certificateMatchRFC 4523
2.5.13.36certificatePairExactMatchRFC 4523
2.5.13.37certificatePairMatchRFC 4523
1.2.36.79672281.1.13.2componentFilterMatchRFC 3687
1.2.36.79672281.1.13.7directoryComponentsMatchRFC 3687
2.5.13.31directoryStringFirstComponentMatchRFC 4517
2.5.13.1distinguishedNameMatch DN equality done properly, component by component, rather than as a string compare. That is why cn=Bob,dc=example and …RFC 4517
2.5.13.27generalizedTimeMatchRFC 4517
2.5.13.28generalizedTimeOrderingMatchRFC 4517
2.5.13.29integerFirstComponentMatchRFC 4517
2.5.13.14integerMatch Equality for INTEGER attributes, comparing numeric value rather than text, so 007 and 7 are the same. Ordering, the …RFC 4517
2.5.13.15integerOrderingMatchRFC 4517
2.5.13.33keywordMatchRFC 4517
1.2.840.113556.1.4.803LDAP_MATCHING_RULE_BIT_AND Bitwise AND matching ruleMS-ADTS
1.2.840.113556.1.4.804LDAP_MATCHING_RULE_BIT_OR Bitwise OR matching ruleMS-ADTS
1.2.840.113556.1.4.1941LDAP_MATCHING_RULE_IN_CHAIN Transitive (nested) group matching ruleMS-ADTS
2.5.13.8numericStringMatchRFC 4517
2.5.13.9numericStringOrderingMatchRFC 4517
2.5.13.10numericStringSubstringsMatchRFC 4517
2.5.13.30objectIdentifierFirstComponentMatchRFC 4517
2.5.13.0objectIdentifierMatch Equality for OID-valued attributes, which is how objectClass filters work under the hood. It compares object …RFC 4517
2.5.13.17octetStringMatchRFC 4517
2.5.13.18octetStringOrderingMatchRFC 4517
2.5.13.22presentationAddressMatchRFC 2252
1.2.36.79672281.1.13.5presentMatchRFC 3687
2.5.13.24protocolInformationMatchRFC 2252
1.2.36.79672281.1.13.3rdnMatchRFC 3687
2.5.13.41storedPrefixMatchRFC 3698
2.5.13.20telephoneNumberMatchRFC 4517
2.5.13.21telephoneNumberSubstringsMatchRFC 4517
2.5.13.23uniqueMemberMatchRFC 4517
1.3.6.1.1.16.2uuidMatchRFC 4530
1.3.6.1.1.16.3uuidOrderingMatchRFC 4530
2.5.13.32wordMatchRFC 4517
← All categories