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:
already logged in LDAP user unable to perform roles assigned to it at user-group level, even after the user is associated to the usergroup at the AD end.
Version-Release number of selected component (if applicable):
sat61-GA-snap4
How reproducible:
Steps to Reproduce:
1. configure LDAP authentication using http://theforeman.org/manuals/1.8/index.html#4.1.1LDAPAuthentication
2. login as a AD user, which is not part of the external user-group
3. As admin user, create a user-group with external user-group (example Active Directory)
4. as admin user, create a ak_role via the roles and assign all the "activation keys" permissions via the filters.
5. as admin user, assign the role "ak_role" at the user_group level
6. associate the user to user-group at the AD end.
7. Now login as a AD user to note that the roles have no effect.
Actual results:
roles have no effect, if the user was logged in before
*) associating the AD user to user-group in AD
Expected results:
Once the AD user is associated to User-group at AD end, the user upon his next login should be able to perform the roles assigned to it at the user-group level.
Additional info:
yes, the user does logs out and logs back in and still cannot see the new roles.
Additional information:
The new roles are only seen, once the user is deleted by the admin and when the LDAP user logs in , he sees the new roles.
We do not want to delete the user for the new roles at user-group level to take effect.
It appears that I need to do two things to get this working properly.
a) make sure that the user's proper orgs is assigned and selected proper orgs or select "Any organization" for the below "refresh" action to take effect for all users.
b) make sure that admin user hits the "refresh" button after the associating of the user to user-group to LDAP, or wait for the cron job to kick-in.
Sorry, I almost missed that we need to hit the "refresh" button, with proper orgs selected for the user.