rancher / dashboard

The Rancher UI
https://rancher.com
Apache License 2.0
459 stars 259 forks source link

Same user allowed to have multiple roles in the same cluster #6184

Open nickwsuse opened 2 years ago

nickwsuse commented 2 years ago

Setup

Describe the bug

To Reproduce

  1. Stand up Rancher instance and a downstream cluster
  2. In the Rancher UI, click the hamburger menu icon in the top left
  3. In the expanded menu on the left side of the page, click "Users & Authentication"
  4. Create a new user by clicking the "Create" button in the upper right of the page
  5. Click the hamburger menu icon again
  6. Click the downstream cluster you created in step 1
  7. In the menu on the left side of the page, click "Cluster Members"
  8. Click the "Add" button in the upper right of the page
  9. In the search box, search for the user you created in step 4
  10. Select any of the Cluster Permissions radio buttons
  11. Repeat steps 8 and 9
  12. Select a different Cluster Permission than what you selected in step 10

Result

Expected Result

Actual Result

Screenshots View of the UI showing a user with multiple conflicting role permissions image

bashofmann commented 2 years ago

Isn't this a feature and the result is that the user has the permissions from both roles combined?

Similarly a user in Kubernetes can have multiple RoleBindings.

gaktive commented 2 years ago

We need to review the UX in a later version. The fact is that there aren't 6 u1 users here; the presentation is that the u1 user has these roles.

Kubernetes can allow for competing cluster permissions but this would be better if we show the u1 user once with the 6 roles. But to add roles, we'd need a different UX.

kwwii commented 2 years ago

We need to redesign the Add User / Permissions functionality at the cluster level. The current UI is confusing and clearly not offering a good UX

dasarinaidu commented 1 year ago

I am seeing the same issue on v2.7-f7692f30cf47d00073cc41b879e0ff90fb0a68b0-head

image

edenhernandez-suse commented 1 year ago

Part of #8233