-
Notifications
You must be signed in to change notification settings - Fork 898
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
While adding a new cloud volume, it is listing all users. #22974
Comments
@SanthoshRam-03 can you provide a screenshot of the user's role? Edit the role and open up the two highlighted sections below: |
Hi @jrafanie , I've updated the role of the user who wants to create a new volume, and its the role of EvmRole-physical_storages_user, but I cannot edit the roles. |
Ok, @SanthoshRam-03 thank you. It does look like the feature permissions look to be correct. I was curious if all of the features below the lower "tenant" were selected. It could be that we are mapping the cloud tenant incorrectly in this situation so we'll look at that next. |
@SanthoshRam-03 is the issue that you're having that "Cloud Tenant" dropdown shows selections that you don't think users should see? |
After looking at it a second time, the non-admin user looks to have all feature permissions in the cloud tenant area, via a white filled checked checkbox, including adding, removing and modifying cloud tenants. In that respect, it's like a cloud tenant administrator. Is it able to do these admin tasks for all cloud tenants or only child tenants? I'm curious what the current desired permissions are for this user and what you're seeing. I would not have expected the "modification" permissions for a non-admin user who shouldn't be able to see other tenants. |
This issue has been automatically marked as stale because it has not been updated for at least 3 months. If you can still reproduce this issue on the current release or on |
Hi @agrare @Fryguy,
When creating a new cloud volume, in the tenant dropdown, it lists all tenants for admin and non-admin users.
The text was updated successfully, but these errors were encountered: