Before reporting an issue
Area
admin/ui
Describe the bug
Starting with Keycloak 26.3.0, a realm-level administrator (user with the realm-admin role in a non-master realm) can no longer use the realm-specific Admin Console.
After authenticating directly against the realm-level console URL (e.g. /admin/<realm>/console/#/), the UI becomes largely unusable: most components do not render correctly and the web console is effectively non-functional.

This workflow worked as expected in 26.2.5 and earlier versions: realm-level administrators were able to access the realm-specific admin console to perform maintenance tasks.
From 26.3.0 through 26.4.7 (latest at time of reporting), realm-level administration appears to be possible only by signing into the master realm Admin Console with a server administrator account and switching to the target realm, which is a functional regression for delegated realm administration.
Version
26.4.7
Regression
Expected behavior
A user with realm-level administrative permissions (e.g., realm-admin in realm Test) should be able to:
- Navigate to the realm-specific Admin Console endpoint: http://localhost:8080/admin/Test/console/#/
- Authenticate successfully
- Use a fully rendered, functional Admin Console UI for that realm (as in 26.2.5 and earlier)
Actual behavior
After logging in to the realm-level Admin Console (/admin/<realm>/console/#/) as the realm admin user:
- The Admin Console UI is broken / mostly not rendered
- Navigation and UI components are not usable
- The console cannot be used to perform administrative tasks from the realm-level entry point
How to Reproduce?
- Install Keycloak 26.3.0+
- Create a realm named
Test
- Create a new user in realm
Test and grant them the realm-admin role
- Open the realm-level Admin Console URL, for example: http://localhost:8080/admin/Test/console/#/
- Log in as the realm-level administrator created in step 3
Observe: the Admin Console UI does not render correctly and is not usable.
Anything else?
No response
Before reporting an issue
Area
admin/ui
Describe the bug
Starting with Keycloak 26.3.0, a realm-level administrator (user with the
realm-adminrole in a non-master realm) can no longer use the realm-specific Admin Console.After authenticating directly against the realm-level console URL (e.g. /admin/<realm>/console/#/), the UI becomes largely unusable: most components do not render correctly and the web console is effectively non-functional.

This workflow worked as expected in 26.2.5 and earlier versions: realm-level administrators were able to access the realm-specific admin console to perform maintenance tasks.
From 26.3.0 through 26.4.7 (latest at time of reporting), realm-level administration appears to be possible only by signing into the master realm Admin Console with a server administrator account and switching to the target realm, which is a functional regression for delegated realm administration.
Version
26.4.7
Regression
Expected behavior
A user with realm-level administrative permissions (e.g.,
realm-adminin realm Test) should be able to:Actual behavior
After logging in to the realm-level Admin Console (/admin/<realm>/console/#/) as the realm admin user:
How to Reproduce?
TestTestand grant them therealm-adminroleObserve: the Admin Console UI does not render correctly and is not usable.
Anything else?
No response