-
Notifications
You must be signed in to change notification settings - Fork 15
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
Domains & SSO still available in "Settings" even if disabled in Style #122
Comments
@MGLL Thanks for the report. I'm not entirely sure this is an issue though. The only way to access the settings page (button present) is if you have the The visibility options can be configured as needed to control the view of the UI. The ability to interact with the API (UI or no) is based on the roles assigned to a user. If they don't have the right role, no settings button for the organization is viewable. As you noted, the permission controls this and you are correct in setting it appropriately for users. |
I think it could be an issue in the case, for example, we want to let an admin in the organization manage the organization but as the admin of the SaaS Platform, we want to restrict / hide something. Also, I noticed that an user which can view roles and invite other users, can select any role (so an user can invite another user with For the first point, I think that's something I could contribute on (however, not sure when) if you have other topics currently 👍 |
Hello, just to notify that I noticed something.
When I disable Domains & SSO in AdminUI of Keycloak (Styles), it disappears from the "organization homepage", but it's still available in settings.
Admin UI:
Organization Homepage:
Organization Settings:
If you want, I could take a look when I have time.
Also, I noticed that "Name" is supposed to be read-only (in UI), but I'm able to change it through API. I will take this into account for my current work on "Read Only Organization Metadata" to set "Name" as read-only by default (for organization user and not platform admin).
The text was updated successfully, but these errors were encountered: