346
Novell eDirectory 8.8 Administration Guide
n
ov
do
cx (e
n)
22
Ju
n
e 20
09
FALSE if it does not match any attribute in the entry.
Undefined if the matchingRule is not recognized or the assertionValue cannot be parsed.
If the type field along with the matchingRule is present, the matchingRule must be one permitted for
use with that type, otherwise the filter item is undefined. If the :dn is specified in the search filter, the
match is applied against all the attributes in an entry’s distinguished name as well, and also evaluates
to TRUE if there is at least one attribute in the distinguished name for which the filter item evaluates
to TRUE. The dnAttributes field is present so that there does not need to be multiple versions of
generic matching rules such as for word matching, one to apply to entries and another to apply to
entries and dn attributes as well.
Essentially, an extensible match filter allows an LDAP client to achieve two objectives:
Support multiple matching rules for same type of data
Include DN elements in the search criteria
The DN specification allows matching on specific elements of the DN.
Novell eDirectory 8.7.3 and later versions support the extensible match filter for matching on the
DN attributes. The other elements of the extensible match search filter, namely the matching rule,
are treated as undefined and ignored. The DN matching allows an LDAP client to drastically reduce
the searches required to locate an object in an eDirectory tree. For example, a complex LDAP search
filter such as
(&(ou:dn:=sales)(objectclass=user))
would let you have a listing of all the User objects in the sales function (that is, anywhere under the
sales containers).
Usage Examples
The following are examples of the string representations of extensible match search filter that are
supported in eDirectory 8.7.3 and later versions.
(o:dn:=Ace Industry)
This example illustrates the use of the :dn notation. The attributes of an entry’s distinguished name
should be considered part of the entry when evaluating the match. It denotes an equality match.
(:dn:2.4.8.10:=Dino)
This example is a filter that should be applied to any attribute of an entry. Attributes contained in the
DN with the matching rule 2.4.8.10 should also be considered.
The following are some examples of the string representation of extensible match search filter that
are
not
supported in eDirectory 8.7.3 and later versions:
(cn:1.2.3.4.5:=John Smith)
This example illustrates a filter that specifies the attributes type cn and value John Smith. It
mandates that the match should be performed by the directory server according to the matching rule
identified by the oid 1.2.3.4.5.
(sn:dn:2.4.6.8.10:=Barbara Jones)
Summary of Contents for EDIRECTORY 8.8 SP5
Page 4: ...4 Novell eDirectory 8 8 Administration Guide novdocx en 22 June 2009...
Page 72: ...72 Novell eDirectory 8 8 Administration Guide novdocx en 22 June 2009...
Page 118: ...118 Novell eDirectory 8 8 Administration Guide novdocx en 22 June 2009...
Page 130: ...130 Novell eDirectory 8 8 Administration Guide novdocx en 22 June 2009...
Page 188: ...188 Novell eDirectory 8 8 Administration Guide novdocx en 22 June 2009...
Page 222: ...222 Novell eDirectory 8 8 Administration Guide novdocx en 22 June 2009...
Page 240: ...240 Novell eDirectory 8 8 Administration Guide novdocx en 22 June 2009...
Page 264: ...264 Novell eDirectory 8 8 Administration Guide novdocx en 22 June 2009...
Page 290: ...290 Novell eDirectory 8 8 Administration Guide novdocx en 22 June 2009...
Page 322: ...322 Novell eDirectory 8 8 Administration Guide novdocx en 22 June 2009...
Page 540: ...540 Novell eDirectory 8 8 Administration Guide novdocx en 22 June 2009...
Page 548: ...548 Novell eDirectory 8 8 Administration Guide novdocx en 22 June 2009...
Page 616: ...616 Novell eDirectory 8 8 Administration Guide novdocx en 22 June 2009...
