Created attachment 1359398 [details] screenshot of UI with org_admin user Description of problem: We created a role with org_admin user and tried to add filters. But could not able to see filters of role with org_admin role. Version-Release number of selected component (if applicable): Satellite 6.3 snap 26 How reproducible: always Steps to Reproduce: 1. Login with admin 2. Navigate to Administer -> Roles 3. Create role cloning Organization admin role 4. Create user providing location, organization and created role 5. Login with created user 6. Create test role 7. Edit role to add new filter 8. Click on role to see added filters. Actual results: Not able to see added filter with org_admin role. (see attachment) Expected results: Added filter should be displayed. Additional info: With admin user, can able to see filters added to role.
Created attachment 1359399 [details] screenshot of UI with admin user
The fact that org admin user could click on role name is a bug, this will be fixed soon by BZ 1502725. Roles should be only readable. There is separate filters page to see permissions for role. This is still a valid bug, since even this page does not list filters for org admin. So this bug effectively is "non-admin users can't can't see role filters". This is caused by the fact, filters are hidden by Taxonomix but in fact these are global resources. In fact there's no point in even having filters permissions, they should be determined by the given role permission.
Created redmine issue http://projects.theforeman.org/issues/21778 from this bug
Upstream bug assigned to mhulan
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21778 has been resolved.
VERIFIED Version tested: Satellite 6.5 snap 4 1.Created user with cloned org admin role. 2.Navigated to roles 3.Clicked on filter User with org admin role is now able to see filters on role.
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/RHSA-2019:1222