#1471 Range Retrieval: Unable to retrieve all members when filter is used in search base.
Closed: Fixed None Opened 11 years ago by kaushikub.

Setup:

  • Add a group with 200 member users in AD
  • Change the value of MaxValRange on the AD Server to 50
  • Verified with ldapsearch to the AD Server, that only a range of 50 members are displayed at a time:

    member;range=0-49: CN=rangeuser03,CN=Users,DC=sssdad,DC=com
    member;range=0-49: CN=rangeuser02,CN=Users,DC=sssdad,DC=com
    member;range=0-49: CN=rangeuser01,CN=Users,DC=sssdad,DC=com
    ....

  1. Lookup the group:
    Result:
    "getent group groupname" returns all 200 users. <== Correct behaviour

  2. Add "ldap_group_search_base = dc=sssdad,dc=com??(cn=groupname)" in sssd.conf domain section
    Result:
    "getent group groupname" only returns first 50 members. <== Should have returned 200 members.

As per the filter, there shouldn't be any restriction on the no. of members being displayed.


Fields changed

summary: Range Retrieval: Unable to retrieve all members when filter is user in search base. => Range Retrieval: Unable to retrieve all members when filter is used in search base.

We need a documentation bug that would set the correct expectations.

This will be a man page update.

milestone: NEEDS_TRIAGE => SSSD 1.9.1
proposed_priority: => Undefined
rhbz: [https://bugzilla.redhat.com/show_bug.cgi?id=848031 848031] => 0

Fields changed

owner: somebody => jhrozek
patch: 0 => 1
status: new => assigned

master: c3869ca

resolution: => fixed
status: assigned => closed

Metadata Update from @kaushikub:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.9.1

7 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/2513

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata