Fix Ldap search for attributes with no substr matching rule

[julien-nc]

Wildcards are not supported when used in search filters for the entryUUID attribute. I guess it's the same for some other attributes as well.

IMO we can make an exact search filter in this case.

Is there a cleaner way to address that issue?

[come-nc]

It’s not limited to entryUUID it’s any field without a substr matching rule.
Maybe we can use something like (|(field=search)(field=search*)) ?

[julien-nc]

@come-nc Much better indeed!

[julien-nc]

@come-nc @blizzz What do you think about the way it's done now with the OR exact_search?

[blizzz]

Do we know whether this might have performance impact? I would assume not, but then I know those products and I would not be surprised…

[julien-nc]

@blizzz I have no idea but I think the partial search we do anyway might be way more costly than the additional exact search.

[blizzz]

@blizzz I have no idea but I think the partial search we do anyway might be way more costly than the additional exact search.

Certainly. What I wonder is whether the products handle this now smartly, or whether this has an additional performace penalty. For sure we cannot go without the appended wildcard for ordinary searches. An alternative would be a list of known attributes for which we do not add the wildcard. But, if this approach works out fine it is preferable – looks duplicated, but less complex.

[come-nc]

@blizzz I have no idea but I think the partial search we do anyway might be way more costly than the additional exact search.

Certainly. What I wonder is whether the products handle this now smartly, or whether this has an additional performace penalty. For sure we cannot go without the appended wildcard for ordinary searches. An alternative would be a list of known attributes for which we do not add the wildcard. But, if this approach works out fine it is preferable – looks duplicated, but less complex.

I think techincally you could query the ldap server for schema information to know which fields have substr matching rules and which have not. But that seems overkill for current situation.

[blizzz]

/rebase