Learn more about these different git repos.
Other Git URLs
Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1583725
Description of problem: SSSD uses the following LDAP query to detect if the AD Global Catalog (GC) server can be used to retrieve POSIX attributes: '(|(&(uidNumber=*)(objectClass=user))(&(gidNumber=*)(objectClass=group)))' The filter is used with a sizelimit of '1' but AD is not properly honoring the sizelimit. This issue is tracked in BZ #1582975. The other issue is that this query should only go to the Global Catalog server but with the current version of SSSD we do see this query also going to regular AD DCs. Version-Release number of selected component (if applicable): sssd-1.16.0-19.el7.x86_64 Steps to Reproduce: 1. Configure SSSD with AD provider. 2. Create an AD account with POSIX attributes 3. Login into the SSSD client using this account Actual results: The LDAP query listed above goes to a regular AD DC. Because of the issue reported in BZ #1582975 it might happen that SSSD runs into a timeout and the next server is contacted. This might end up in an infinite loop until the search can be completed. Expected results: LDAP query goes only to AD GC server. Additional info: This is a possible regression.
Metadata Update from @jhrozek: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1583725
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 1.16.3
Metadata Update from @jhrozek: - Issue assigned to jhrozek
Metadata Update from @jhrozek: - Issue priority set to: major - Issue tagged with: PR, bug
PR: https://github.com/SSSD/sssd/pull/603
master: 5e1641b
Metadata Update from @fidencio: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
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/4760
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.
Login to comment on this ticket.