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

Domains & SSO still available in "Settings" even if disabled in Style #122

Closed
MGLL opened this issue Dec 26, 2023 · 2 comments · Fixed by #157
Closed

Domains & SSO still available in "Settings" even if disabled in Style #122

MGLL opened this issue Dec 26, 2023 · 2 comments · Fixed by #157

Comments

@MGLL
Copy link
Contributor

MGLL commented Dec 26, 2023

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:
AdminUI_Style

Organization Homepage:
OrgPage

Organization Settings:
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).

@pnzrr
Copy link
Contributor

pnzrr commented Dec 27, 2023

@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 manage-organization role.

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.

@MGLL
Copy link
Contributor Author

MGLL commented Dec 27, 2023

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.
With this example, if we disable the SSO & Domains globally and assign the manage-organization to a user, this user can still access the disabled elements through settings.

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 manage-organization even if is roles are "lower" (just invite someone else)).

For the first point, I think that's something I could contribute on (however, not sure when) if you have other topics currently 👍

@pnzrr pnzrr linked a pull request Oct 3, 2024 that will close this issue
@xgp xgp closed this as completed in #157 Oct 3, 2024
xgp pushed a commit that referenced this issue Oct 3, 2024
* fixes #147

* fix Domain feature flag doesn't hide domain settings #155

* fix Localizations for spanish are missing in Portal #154

* fix Domains & SSO still available in "Settings" even if disabled in Style #122

* update API from openAPI spec

* add in pending invites page
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants