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:
Per 6.3 planning, moving out non acked bugs to the backlog
I believe this has been fixed in Satellite 6.2, external user groups are refreshed on login.
This was delivered in 6.2. Closing this out as Current Release.