Re: Schema matching rules don't work (ITS#3118)

[Kurt@OpenLDAP.org]

At 02:59 PM 4/27/2004, pierangelo.masarati@sys-net.it wrote:
>Full_Name: Pierangelo Masarati
>Version: HEAD
>OS: Irrelevant
>URL: ftp://ftp.openldap.org/incoming/
>Submission from: (NULL) (81.72.89.40)
>
>
>Schema matching rules do not work.  Whan using matched values control to extract
>schema items, the sequence is numericoidValidate(), which fails if anything but
>an OID is used, followed by firstComponentNormalize(), which fails if anything
>but "( OID..." is provided.  So there's no way a macth can occur.  So 
>
>ldapsearch -b 'cn=subschema' -s base -E mv="(attributeTypes=\28 2.5.18.2 \29)

This should be invalid.  The assertion syntax for the equality
rule is OID.

>fails because there's more than an OID in the value, while
>
>ldapsearch -b 'cn=subschema' -s base -E mv="(attributeTypes=2.5.18.2)
>
>fails at firstComponentNormalize() because there are no brackets.

This should be valid.

Likewise for search filters should work the same.

>I guess the
>solution would be to relax constraints in firstComponentNormalize(), and let it
>skip brakets if they're there without requiring their presence.

The right fix is for firstComponentNormalize to realize that
it's dealing with the assertion syntax not the attribute
syntax here.