Red Hat Bugzilla – 1280207 – Unable to resolve group memberships for AD users when using sssd-1.12.2-58.el7_1.6.x86_64 client in combination with ipa-server-3.0.0-42.el6.x86_64 with AD Trust
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.
Unable to resolve group memberships for AD users when using sssd-1.12.2-58.el7_1.6.x86_64 client in combination with ipa-server-3.0.0-42.el6.x86_64 with AD Trust
Identity Management (IdM) clients that are views-enabled are unconditionally looking for a views-related attribute. If the attribute was not available, earlier versions of IdM returned a different error code than later versions, which was not handled as expected on the client side. Consequently, Active Directory (AD) user's group membership resolution failed, as the lookup request failed after not being able to dereference the view name. To fix this bug, if the LDAP_UNAVAILABLE_CRITICAL_EXTENSION(12) or LDAP_PROTOCOL_ERROR(2) error is returned, the error is ignored and the client assumes the server is not views-aware. As a result, AD user's group membership resolution no longer fails when a Red Hat Enterprise Linux 7 client is enrolled to a Red Hat Enterprise Linux 6 server.
IPA SERVER and CLIENT version:
-----------------------------------
ipa-server-3.0.0-47.el6_7.1.x86_64
ipa-client-3.0.0-47.el6_7.1.x86_64
AD Server details: Windows Server 2012 R2
Verified the bug with following steps:
------------------------------------------------
1. As per the verification steps mentioned inside bug #1263262, verified that the group memberships are correctly displayed, when user logs into the system setup with trust environment.
2. Refer the attached log for verification steps.
Thus marking the status of the bug to "VERIFIED".
IPA SERVER and CLIENT version:
-----------------------------------
ipa-server-4.2.0-15.el7_2.3.x86_64
ipa-client-3.0.0-47.el6_7.1.x86_64
AD Server details: Windows Server 2012 R2
Also verified the bug with following steps:
------------------------------------------------
1. Configure IPA server with Active Directory trust setup.
2. Once the trust is setup, executed the steps mentioned inside bug #1263262, verified that the group memberships are correctly displayed, when user logs into the system setup with trust environment.
3. Refer the attached log "verification_bz1280207_72" for verification steps.
Thus marking the status of the bug to "VERIFIED".
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://rhn.redhat.com/errata/RHBA-2015-2634.html