Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
Description of problem:
If the AD server is 2019 R2 version and the user is part of many groups it takes too much time to log in.
Version-Release number of selected component (if applicable):
Satellite 6.10.
How reproducible:
Always
Steps to Reproduce:
1. Configure AD 2019 R2 authentication with Satellite 6.10.
2. Try to login with a user who is part of many groups.
Actual results: The login process takes too much time.
Expected results: The login process should be faster/as usual.
We have included the above fix in our upcoming 7.0 release and are including it here as a hotfix available for Satellite 6.10.
*** Satellite 6.10.X Hotfix Available ***
1) Download tfm-rubygem-ldap_fluff-0.6.0-1.el7sat.noarch.rpm from this bugzilla to your Satellite
2) stop services:
satellite-maintain service stop
3) Install:
rpm -Uvh tfm-rubygem-ldap_fluff-0.6.0-1.el7sat.noarch.rpm
4) restart:
satellite-maintain service start
5) resume operations
Verified this with Satellite 7.0 Snap 12 with AD 2019 Server.
Created User AD Server => Added that user in multiple user groups in AD Server => Satellite Configure with AD Server => Login using the AD Server user
Login was quick enough. Issue no more reporducible.
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 (Moderate: Satellite 6.11 Release), 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-2022:5498