-
Notifications
You must be signed in to change notification settings - Fork 162
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
[BUG] UI is not reflecting the correct Mapped Users #1188
Comments
[Triage] @RyanL1997 Can you look into this issue to see what the scenario is, technically this looks correct, however this behavior is confusing to users. @shanilpa Can you look into how we want to support these scenarios? |
@peternied , I would also like to contribute on this |
Hi @devardee, thanks for filling this issue. Here are some outputs from my side according to the reproduction of this issue:
As you can see, even the roles mapping shows correct in the panel of step 3., the field of |
Closing as expected behavior, please re-open with more details if that is not the case. |
What is the bug?
When we create user and map roles using API, role mapping is not reflected in UI of "Mapped Users" section.
How can one reproduce the bug?
Steps to reproduce the behavior:
Go to Security -> Internal Users and you will be able to see that user has been created.
Now go to Security -> Roles -> all_access and you will find that the newly created user is not mapped to "all_access" role in "Mapped Users" section. I am attaching screenshot for your reference.
However when you describe the user using below API call, you can see that "all_access" is mapped to user and user will be able to perform all actions on the domain.
What is the expected behavior?
Security -> Roles -> all_access should show all the users mapped to a role
What is your host/environment?
Do you have any screenshots?
If applicable, add screenshots to help explain your problem.
Do you have any additional context?
Add any other context about the problem.
The text was updated successfully, but these errors were encountered: