Bug 1380603 - WebUI: Control Explorer module is enabled despite the restriction for default roles
Summary: WebUI: Control Explorer module is enabled despite the restriction for default...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: cfme-future
Assignee: Hilda Stastna
QA Contact: Dave Johnson
URL:
Whiteboard: ui:control
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-30 05:30 UTC by Ramesh A
Modified: 2018-03-15 14:12 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-15 14:12:56 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:


Attachments (Terms of Use)
default role access (150.51 KB, image/png)
2016-09-30 05:30 UTC, Ramesh A
no flags Details
control-explorer (140.00 KB, image/png)
2016-09-30 05:32 UTC, Ramesh A
no flags Details

Description Ramesh A 2016-09-30 05:30:54 UTC
Created attachment 1206139 [details]
default role access

Description of problem:
Explorer is enabled despite the restriction for default roles

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

How reproducible:
Very

Steps to Reproduce:
1. As admin create a new user and assign a default group whose role does not contain Control Explorer access (say EvmRole-approver or EvmRole-auditor, etc..)
2. Login as newly created user and check for the Control module access


Actual results:
Displays Control Explorer and is able to access despite access restriction in the role. Refer the screenshots for more information

Expected results:
Should not display the Control Explorer.

Additional info:

Comment 2 Ramesh A 2016-09-30 05:32:00 UTC
Created attachment 1206140 [details]
control-explorer

Comment 5 Hilda Stastna 2018-03-15 14:12:56 UTC
I am closing the bug because it is no longer present. Tested in 5.8, 5.9 and on latest 'master' branch.


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