Description of problem: In some scenarios, RHV-M displays incorrect permission for the users. This only happens with normal user and not with admin@internal user. Please see "Steps to Reproduce" for more info. Version-Release number of selected component (if applicable): rhevm-4.1.1.8-0.1.el7.noarch How reproducible: 100% Steps to Reproduce: 1. Create two groups group_a and group_b and add a user_a to group_a and user_b to group_b. ovirt-aaa-jdbc-tool group-manage show group_a Group: group_a(f497038d-98a3-44c8-a9c3-88ecb3654d66) members: User: user_a ovirt-aaa-jdbc-tool group-manage show group_b Group: group_b(29ceab89-df25-47bc-a4aa-f44f5b6d9271) members: User: user_b 2. Assign group_a as superuser on system object. 3. Login to admin portal with user_a. 4. Check the permission of user_b . Admin portal will show user_b has superuser role which is inherited from group_a although user_b is not a member of group_a. 5. This is only a "display" issue and user_b don't really have this permission and login to admin portal will fail for this user. Actual results: Permission is not shown correctly Expected results: Permission should show correctly Additional info: Attaching screenshots from my test environment. The customer who reported this issue is using AD .
Created attachment 1281820 [details] directory_group_user_a
Created attachment 1281821 [details] directory_group_user_b
Created attachment 1281822 [details] user_b incorrect permission
Ondro, could you please take a look?
It always shows the group, which is the current logged in user part of. This is UI issue.
WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Found clone flags: ['rhevm-4.1.z', 'rhevm-4.2-ga'], ] For more info please contact: rhv-devops: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Found clone flags: ['rhevm-4.1.z', 'rhevm-4.2-ga'], ] For more info please contact: rhv-devops
Verified with: ovirt-engine-4.2.0-0.0.master.20171010095230.git721740e.el7.centos.noarch
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, 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/RHEA-2018:1488
BZ<2>Jira Resync