You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Keycloak Admin Console: Out of memory when visting admin console for one realm
#15119
We use Keycloak with many realms (>700) and we have always had the problem of not being able to access the admin console via the master realm because of the long duration of the whoami endpoint. To circumvent this, we access the admin console for one specific realm with a user that only exists in this realm and has the management roles from the management client.
We currently switching from Keycloak Legacy (18.0.0) to Keycloak.X (18.0.2) and this workaround does not work any more: The admin console is unusable due to a infinite loading of the /auth/admin/realms?briefRepresentation=true call which also might lead to an out of memory error of the Keycloak. With the WildFly-based distribution, this was not a problem.
Has anybody a similar issue and a workaround? Do we need to enlarge some caches, for example?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hey everybody,
We use Keycloak with many realms (>700) and we have always had the problem of not being able to access the admin console via the
masterrealm because of the long duration of thewhoamiendpoint. To circumvent this, we access the admin console for one specific realm with a user that only exists in this realm and has the management roles from themanagementclient.We currently switching from Keycloak Legacy (18.0.0) to Keycloak.X (18.0.2) and this workaround does not work any more: The admin console is unusable due to a infinite loading of the
/auth/admin/realms?briefRepresentation=truecall which also might lead to an out of memory error of the Keycloak. With the WildFly-based distribution, this was not a problem.Has anybody a similar issue and a workaround? Do we need to enlarge some caches, for example?
All reactions