This bug is created as a clone of upstream ticket:
If you have an attribute with Directory String syntax defined with caseExact matching rules, and a value with upper case letters, a search will not find the value because the search filter will be normalized using the default normalization for the syntax instead of being aware of the matching rule. value normalization must take into account the matching rule used.
Verification of this should already be covered by the acceptance tests.
filter tet suit is passing 100%.
Hence marking this bug as VERIFIED.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Cause: Attempting to perform a search on an attribute that is defined with a matching rule that uses a different comparison than the default comparison for the attributes syntax.
Consequence: Searches do not work properly.
Fix: Use a matching rule sensitive normalization on filter attributes and values.
Result: Searches return matching rule valid results.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.