Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionThorsten Scherf
2018-05-29 14:37:05 UTC
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.
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.
https://access.redhat.com/errata/RHSA-2018:3158