Bug 1531499 - Automation->Ansible is visible for multiple roles when it should not be
Summary: Automation->Ansible is visible for multiple roles when it should not be
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: GA
: 5.8.4
Assignee: lgalis
QA Contact: Mike Shriver
Whiteboard: rbac:ansible
Depends On:
TreeView+ depends on / blocked
Reported: 2018-01-05 10:42 UTC by Antonin Pagac
Modified: 2018-06-25 14:17 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-06-25 14:17:08 UTC
Category: Bug
Cloudforms Team: Ansible
mshriver: automate_bug+

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:1972 None None None 2018-06-25 14:17:52 UTC
Red Hat Bugzilla 1525598 None None None Never

Internal Links: 1525598

Description Antonin Pagac 2018-01-05 10:42:22 UTC
Description of problem:
Automation -> Ansible is visible in the vertical navigation for roles that don't have permission to access it. These roles are affected:


Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create user with any of the roles listed above
2. Login as created user
3. Notice visibility of Automation->Ansible in vertical nav

Actual results:
Automation->Ansible is visible

Expected results:
Automation->Ansible should not be visible

Additional info:
Tested with a ldap user.

Comment 8 Mike Shriver 2018-04-17 15:09:56 UTC
Testing in CFME

EvmRole_administrator, EvmRole-user_self_service, EvmRole-vm_user roles now have Automation->Ansible access in RBAC tree and see the pages in navigation [PASS]

EvmRole-desktop: RBAC does not include Automation->Ansible, and the pages are NOT visible in navigation. [PASS]

The role's RBAC access concerning Automation->Ansible has been resolved.

Comment 10 errata-xmlrpc 2018-06-25 14:17:08 UTC
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.


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