Bug 1779493

Summary: Topology edit actions should be disabled if the user does not have correct permission
Product: OpenShift Container Platform Reporter: Vikram Raj <viraj>
Component: Dev ConsoleAssignee: Vikram Raj <viraj>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: aos-bugs, cvogt, gamore, nmukherj
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1779915 (view as bug list) Environment:
Last Closed: 2020-05-04 11:18:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Vikram Raj 2019-12-04 04:52:39 UTC
Description of problem:
If the user does not have permission to perform these actions they should not be shown / available.

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


How reproducible:


Steps to Reproduce:
1. Log in as a non-admin user. And visit the topology page of a project which is not created by you.
2. On hover over a node, you will see the connector, context menu by right-clicking on the node and able to regroup by drag and drop of the node.

Actual results:
On hover over a node, you will see the connector, context menu by right-clicking on the node and able to regroup by drag and drop of the node.

Expected results:
If the user has only read access to a namespace then on hover over a node, the user should not see the connector, should not see the context menu on right-click on a node and not able to regroup the application by drag and drop.

Additional info:

Comment 2 Gajanan More 2020-03-04 12:32:48 UTC
I have validated this bug on 
Build:4.4.0-0.nightly-2020-03-04-000622 
Browser:Google Chrome Version 78.0.3904.108
Marking this bug as verified

Comment 4 errata-xmlrpc 2020-05-04 11:18:30 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.

https://access.redhat.com/errata/RHBA-2020:0581