Bug 1615163 - Server side search with matching rules returns non-sorted results
Summary: Server side search with matching rules returns non-sorted results
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: 389-ds-base
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: pre-dev-freeze
: 8.2
Assignee: mreynolds
QA Contact: RHDS QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-12 21:18 UTC by Viktor Ashirov
Modified: 2019-08-01 15:27 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)

Description Viktor Ashirov 2018-08-12 21:18:22 UTC
Description of problem:
If matching rule is used for server side search, it returnes non-sorted results.

Version-Release number of selected component (if applicable):
389-ds-base-1.3.8.4-10.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. Install IPA and add some entries
2. Run ldapsearch with sss control and matching rule
3.

Actual results:
[root@server ds]# ldapsearch -xLLL -D cn=Directory\ Manager -w Secret123 -b cn=users,cn=accounts,dc=ipa,dc=test -E sss=uid:2.5.13.3 "(uid=tuser*)" uid | grep uid:
uid: tuser2
uid: tuser3
uid: tuser
[root@server ds]# ldapsearch -xLLL -D cn=Directory\ Manager -w Secret123 -b cn=users,cn=accounts,dc=ipa,dc=test -E sss=-uid:2.5.13.3 "(uid=tuser*)" uid | grep uid:
uid: tuser2
uid: tuser3
uid: tuser


Expected results:
Results should be sorted.

Additional info:
See also https://pagure.io/389-ds-base/issue/49509
and https://bugzilla.redhat.com/show_bug.cgi?id=1607078


Note You need to log in before you can comment on or make changes to this bug.