[Date Prev][Date Next]
In yet another attempt to make more use of server's subschema in web2ldap I'm
looking more closely at matchingRuleUse in OpenLDAP's subschema subentry.
What's the base for the matchingRuleUse values generated by slapd?
RFC 4512 is pretty terse on this:
APPLIES provides a list of attribute types the matching rule
Ah, well... :-/
Basically I wonder why I can't use this filter and why
caseIgnoreIA5SubstringsMatch is not listed as being applicable to
Yes, I know: krbPrincipalName is correctly declared with
But what's the reason you cannot override the equality matching with this
extensible filter? Normalization issues when indexing?