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.
0001-Ticket-279-filter-normalization-does-not-use-matchin.patch 0001-Ticket-279-filter-normalization-does-not-use-matchin.patch
To ssh://git.fedorahosted.org/git/389/ds.git c08e877..7b03c97 master -> master commit changeset:7b03c97/389-ds-base Author: Rich Megginson rmeggins@redhat.com Date: Thu Feb 2 20:53:49 2012 -0700 Reviewed by: nhosoi (Thanks!) Branch: master Fix Description: When normalizing the values in a filter, the normalization must take into account the type of filter being used, and the matching rules associated with the attribute, corresponding to the type of filter. Added a mr_normalize function for matching rules. This is primarily needed by the cis and ces associated matching rules, for the case where the normalization function provided by the syntax is different than the one associated with the matching rule. For example, Directory String (cis) by default uses a case insensitive normalization function, but if you are using a caseExact matching rule you must use a case sensitive normalization function. Added the new function slapi_attr_value_normalize_ext() to allow passing in the type of search filter to normalize for. Platforms tested: RHEL6 x86_64, Fedora 16 Flag Day: yes - plugin structure size change Doc impact: yes - document the new function
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=788725
Added initial screened field value.
Metadata Update from @nkinder: - Issue assigned to rmeggins - Issue set to the milestone: 1.2.10.rc1
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/279
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.