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:-
The first time a user login will always fail when try to login through Active Directory User even that user group is mapped.
Version-Release number of selected component (if applicable):
How reproducible: Always for first time after configuring User group for Active directory authentication in satellite
Steps to Reproduce:
1). Configure Active directory User group successfully.
2). Now try to login to Satellite through Active directory user.
3). It will fail for first time, however after sometime, it will login without any issues.
4). Following command is required to run after configuring any new AD user for successful login:-
---
foreman-rake ldap:refresh_usergroups
---
It is not practical in a production environment. Alternatively, user can wait for up to 30 minutes for the cron job kicking in, which is both inconvenient and confusing.
Actual results:- Fails when try to login for first time.
Expected results: Should Login immediately after configuring new user/group.
Additional info: