[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Unique identifiers for LDAP attributes
> Though I agree with the general notion of moving toward the use of
> unique OIDs, there's a minor flaw with this statement.
>
> objectIdentifierFirstComponentMatch uses the OID syntax which can
> either be a numericoid (1.2.3.4) or the descr form (cn), so it's still
> usable with short names as it stands today.
You have now hit on a bit of rfc2252 which is particularly hard to
understand, viz:
>From 8.1
If the client supplies a filter using an
objectIdentifierMatch whose
matchValue oid is in the "descr" form, and the oid is
not recognized
by the server, then the filter is Undefined.
David
> Jim
>
>
***************************************************
David Chadwick
IS Institute, University of Salford, Salford M5 4WT
Tel +44 161 295 5351 Fax +44 161 745 8169
Mobile +44 790 167 0359
Email D.W.Chadwick@salford.ac.uk
Home Page http://www.salford.ac.uk/its024/chadwick.htm
Understanding X.500 http://www.salford.ac.uk/its024/X500.htm
X.500/LDAP Seminars http://www.salford.ac.uk/its024/seminars.htm
Entrust key validation string MLJ9-DU5T-HV8J
***************************************************