Bug 1811757

Summary: RBAC check incorrect for Home -> Overview nav item
Product: OpenShift Container Platform Reporter: Samuel Padgett <spadgett>
Component: Management ConsoleAssignee: Samuel Padgett <spadgett>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.4CC: aos-bugs, jokerman, xiaocwan
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, the Home -> Overview nav item would be hidden from users who could not list namespaces, but otherwise had authority to see metrics. The nav item now appears for all users who have authority to see cluster metrics.
Story Points: ---
Clone Of:
: 1812506 (view as bug list) Environment:
Version: 4.4.0-0.ci-2020-03-09-103610 Cluster ID: 409bf8c6-8338-44de-92aa-694c2b61aa26 Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:73.0) Gecko/20100101 Firefox/73.0
Last Closed: 2020-07-13 17:19:06 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:
Bug Depends On:    
Bug Blocks: 1812506    
Attachments:
Description Flags
POST get namespace request on Overview page none

Description Samuel Padgett 2020-03-09 17:09:26 UTC
The RBAC check we have is whether the user can list namespaces. The correct check is whether the user can *get* namespaces.

Comment 4 XiaochuanWang 2020-03-11 08:20:19 UTC
Created attachment 1669191 [details]
POST get namespace request on Overview page

Comment 5 XiaochuanWang 2020-03-11 08:23:21 UTC
Home -> Overview page now POST a request to get namespace by api/kubernetes/apis/authorization.k8s.io/v1/selfsubjectaccessreviews and reture 201 without issue.

Now this could be Verified.
Checked on 4.5.0-0.ci-2020-03-10-225406

Comment 7 errata-xmlrpc 2020-07-13 17:19:06 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:2409