Bug 1544875 - Role inconsistency with privileges when creating reports and setting chargeback filters
Summary: Role inconsistency with privileges when creating reports and setting chargeba...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Reporting
Version: 5.8.0
Hardware: All
OS: All
high
medium
Target Milestone: GA
: 5.10.0
Assignee: Libor Pichler
QA Contact: Landon LaSmith
URL:
Whiteboard:
Depends On:
Blocks: 1553776 1565835
TreeView+ depends on / blocked
 
Reported: 2018-02-13 16:40 UTC by Ryan Spagnola
Modified: 2021-06-10 14:36 UTC (History)
4 users (show)

Fixed In Version: 5.10.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1553776 1565835 (view as bug list)
Environment:
Last Closed: 2019-02-11 14:03:37 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ryan Spagnola 2018-02-13 16:40:40 UTC
Description of problem:
When creating a user with the EvmRole-administrator or EvmRole_super_administrator the user is able to set owner of a report under chargeback filters. When copying this role this privilege does not exist.

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

How reproducible:
Always

Steps to Reproduce:
1. copy one of the roles above to a new role and assign to a user
2. log in as that user and create a report
3. attempt to change the owner of the report the field is locked

Actual results:


Expected results:


Additional info:

Comment 6 Landon LaSmith 2018-08-06 01:14:04 UTC
Kicking this back since the default admin role and copied admin role can no longer set the owner under chargeback filters b/c the owner pull down is not populated with any rbac users. Only the default super admin role and customer roles with Everything enabled are able to select other users when setting the owner under chargeback filters.

Comment 10 Landon LaSmith 2018-10-22 16:28:42 UTC
VERIFIED in 5.10.0.20.


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