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

Authorization tab for master-client shows up in odd ways #29423

Closed
1 of 2 tasks
Jamstah opened this issue May 9, 2024 · 1 comment
Closed
1 of 2 tasks

Authorization tab for master-client shows up in odd ways #29423

Jamstah opened this issue May 9, 2024 · 1 comment
Labels

Comments

@Jamstah
Copy link
Contributor

Jamstah commented May 9, 2024

Before reporting an issue

  • I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.

Area

admin/ui

Describe the bug

When you first start keycloak, the master-realm client has no Authorization tab.

If you turn on fine-grained permissions for any client, the master-realm then has the Authorization tab.

Turning permissions off does not result in the Authorization tab going away again.

This is causing test failures in the admin-ui E2E tests, because the number of tabs is tested for this client and will vary depending on which tests have been run before it in that container.

Version

main

Regression

  • The issue is a regression

Expected behavior

Existence of Authorization tab should be predictable

Actual behavior

Authorization tab may or may not exist based on previous tests

How to Reproduce?

  1. Create an empty server using --features=admin-fine-grained-authz
  2. Check the number of tabs in the master-realm client
  3. Turn permissions on in a client
  4. Check the number of tabs in the master-realm client
  5. Turning permissions back off, or deleting the client, does not affect the number of tabs

Anything else?

No response

@hmlnarik
Copy link
Contributor

Thank you for reporting this bug. I am closing it in favour of #29443 since the latter targets core functionality where this bug report belongs. Feel free to watch that issue.

@sschu sschu reopened this May 13, 2024
@sschu sschu closed this as not planned Won't fix, can't repro, duplicate, stale May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants