Bug 1221979 - already logged in LDAP user unable to perform roles assigned to it at user-group level
Summary: already logged in LDAP user unable to perform roles assigned to it at user-g...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Users & Roles
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-15 11:45 UTC by Kedar Bidarkar
Modified: 2017-02-23 20:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-05-15 16:23:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Kedar Bidarkar 2015-05-15 11:45:47 UTC
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:

Comment 2 Brad Buckingham 2015-05-15 15:14:03 UTC
Kedar,  In this particular case, is it correct that the user logs out and logs back in that they do not see the updated roles?

Comment 3 Kedar Bidarkar 2015-05-15 15:18:33 UTC
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.

Comment 4 Kedar Bidarkar 2015-05-15 16:23:55 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.