Given what you presented, the filter doesn't match anything -- yet. You
need some entries with an oid attribute:
dn: cn=some entry
oid: 1.2.3.4
dn: cn=some other entry
oid: foo
objectIdentifierMatch has nothing to do with OIDs (or names) defined in a
schema.
Did you have something else in mind?
John McMeeking
Hallvard B Furuseth
<h.b.furuseth@usit.u To: ietf-ldapbis@OpenLDAP.org
io.no> cc:
Sent by: Subject: objectIdentifierMatch on ambiguous name
owner-ietf-ldapbis@O
penLDAP.org
01/02/2003 06:10 AM
What does filter component (oid=foo) applied to attribute oid=bar
evaluate to if the schema defines the following?
object class ( ... NAME 'foo' ... )
object class ( ... NAME 'bar' ... )
attribute type ( ... NAME ('foo' 'bar') ... )
attribute type ( ... NAME 'oid'
EQUALITY objectIdentifierMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.38 ) ; OID
--
Hallvard