Visual RFC.
ALL RFCs / RFC 4515
Read the RFC ↗
RFC 4515 / LDAP FILTER STRINGS

Choose a matching rule explicitly

05

Extensible matching can name a rule and include attributes from an entry's distinguished name.

RFC 4515 · § 4EXAMPLE
4 / 4
Choose a matching rule explicitlyExtensible matching can name a rule and include attributes from an entry's distinguished name. (:caseExactMatch:=Mira) omits the attribute and applies to supporting attributes. Omitting both attribute and rule would not fit the string grammar.Extensible matching fields(:caseExactMatch:=Mira)Attribute: omitted · rule: presentApplies to attributes supporting the ruleNo attribute AND no rule: invalid shapeMatching is still subject to access controlsRFC4515 · chapter 5 · state 4 · fictional examples
04
Omit the attribute, keep the rule

(:caseExactMatch:=Mira) omits the attribute and applies to supporting attributes. Omitting both attribute and rule would not fit the string grammar.

Source for this drawing: RFC 4515 · Read RFC section 4 ↗

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
New to this? Start hereA quick picture + helpful background

A message needs an address.

Think of a packet as a small addressed envelope. Devices pass it onward; transport protocols decide what delivery promises an application gets.

Helpful first, if these ideas are unfamiliar

These pictures are analogies to help you learn. The linked RFC explains the actual rules.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

KEY POINT

Simple comparisons use =, ~=, >= or <=. Approximate and ordering behavior comes from the server's matching rules, not JavaScript lexical order or a universal fuzzy-search algorithm.

  • Simple comparisons use =, ~=, >= or <=. Approximate and ordering behavior comes from the server's matching rules, not JavaScript lexical order or a universal fuzzy-search algorithm.
  • In (cn:caseExactMatch:=Mira), cn is the attribute, caseExactMatch names a matching rule, and := introduces the assertion. The server must support an appropriate rule; the name is not a promise that every server supports it.
  • Adding :dn asks the match to consider suitable attributes from the entry's distinguished name (DN), its structured directory name. It does not select a different search subtree.
  • If the attribute is omitted, a matching rule is required and the match applies to attributes that support it. With an attribute present the matching rule may be omitted, as in (cn:=Mira). DN-attribute matching defaults to false. Unknown or inappropriate rules can evaluate to Undefined.
DETAILS

RFC4515 §4 and RFC4511 §4.5.1.7.7 describe extensible matching. The :dn marker is case insensitive, so :DN is also valid. This guide does not emulate schema discovery, authentication, access control or an arbitrary directory matching engine.

Read the RFC section ↗

All chapters in RFC 4515

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗