Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cluster Member access shouldn't be allowed to navigate to Edit Cluster page #25516

Closed
izaac opened this issue Feb 21, 2020 · 5 comments
Closed
Assignees
Labels
kind/bug Issues that are defects reported by users or that we know have reached a real release team/ui
Milestone

Comments

@izaac
Copy link
Contributor

izaac commented Feb 21, 2020

What kind of request is this (question/bug/enhancement/feature request):
Bug

Steps to reproduce (least amount of steps as possible):

  • Install Rancher 2.4 master-head (02/21/2020) commit id: dad5836
  • Create a new test user testuser1 in Global -> Security -> Users.
  • Create a Custom Cluster, is not necessary to add the nodes. (Cluster will be in Provisioning state).
  • Add this testuser1 as Cluster Member and save the cluster.
  • Login as testuser1 and Global -> Clusters -> Edit

Result:

The user is able to see the Edit page, but this user is not allowed to edit the cluster (only projects).

Screen Shot 2020-02-21 at 11 17 45 AM

Other details that may be helpful:

Environment information

  • Rancher version: 2.4 master-head (02/21/2020) commit id: dad5836
  • Installation option (single install/HA): single
@izaac izaac added the kind/bug Issues that are defects reported by users or that we know have reached a real release label Feb 21, 2020
@izaac izaac added this to the v2.4 milestone Feb 21, 2020
@izaac izaac self-assigned this Feb 21, 2020
@izaac izaac added the team/ui label Feb 21, 2020
@izaac
Copy link
Contributor Author

izaac commented Feb 21, 2020

This is also reproducible in Rancher v2.3.5

@sangeethah
Copy link
Contributor

sangeethah commented Feb 24, 2020

We should be able to suppress the forbidden error message that shows up in this page , if we are not able to restrict access to "Edit cluster" page.

@vincent99
Copy link
Contributor

This is the lack of "dynamic RBAC" and not new or specific to clusters. The API does not provide the information to know if you can edit or not in advance. #11165

@westlywright
Copy link
Contributor

I can fix the double messages though.

@westlywright
Copy link
Contributor

@sangeethah @izaac I spoke too soon. The error messages you are seeing are valid. Part of creating a custom cluster is getting/creating a cluster token. The first thing the UI does is check for the existence of the token and if we don't have one we create a new one. In this case because of the users permissions they do not have access to the cluster token and we try to create one. Since we dont have dynamic RBAC there is no way for the UI to know that this is a permissions issue and hence hide those messages. Until the UI has dynamic RBAC there is not much we can do about any of this.

@westlywright westlywright removed their assignment Mar 6, 2020
@zube zube bot removed the [zube]: Working label Mar 6, 2020
@zube zube bot removed the [zube]: Done label Oct 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issues that are defects reported by users or that we know have reached a real release team/ui
Projects
None yet
Development

No branches or pull requests

5 participants