Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 788725 - filter normalization does not use matching rules
filter normalization does not use matching rules
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: 389-ds-base (Show other bugs)
6.3
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Rich Megginson
IDM QE LIST
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2012-02-08 17:02 EST by Rich Megginson
Modified: 2012-06-20 03:13 EDT (History)
3 users (show)

See Also:
Fixed In Version: 389-ds-base-1.2.10.0-1.el6
Doc Type: Bug Fix
Doc Text:
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.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-20 03:13:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:0813 normal SHIPPED_LIVE Low: 389-ds-base security, bug fix, and enhancement update 2012-06-19 15:29:15 EDT

  None (edit)
Description Rich Megginson 2012-02-08 17:02:11 EST 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/279

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.
Comment 1 Nathan Kinder 2012-02-13 16:46:42 EST 
Verification of this should already be covered by the acceptance tests.
Comment 3 Amita Sharma 2012-05-07 07:08:56 EDT 
filter tet suit is passing 100%.
Hence marking this bug as VERIFIED.
Comment 4 Rich Megginson 2012-05-18 11:13:08 EDT 
clearing needinfo
Comment 5 Rich Megginson 2012-05-24 19:24:32 EDT 
    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.
    
    New Contents:
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.
Comment 6 errata-xmlrpc 2012-06-20 03:13:26 EDT 
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.

http://rhn.redhat.com/errata/RHSA-2012-0813.html
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.