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
After upgrading to Keycloak 26.2, we disabled the feature “admin-fine-grained-authz:v1” according to the upgrade guide to switch to the default version v2.
For the automated configuration we use the Adorsys keycloak-config-cli (version 6.4.0). When the configuration is imported, this breaks in Keycloak with the error message:
Uncaught server error
jakarta.ws.rs.WebApplicationException: Feature not enabled
at org.keycloak.utils.ProfileHelper.requireFeature(ProfileHelper.java:32)
at org.keycloak.services.resources.admin.ClientResource.getManagementPermissions(ClientResource.java:709)
at org.keycloak.services.resources. admin.ClientResource$quarkusrestinvoker$getManagementPermissions_b24e12396765ddf0227c3e87bd0f349a257b683f.invoke(Unknown Source)
at org.jboss.resteasy.reactive.server.handlers.InvocationHandler.handle(InvocationHandler.java:29)
....
V1 is probably still expected at the ClientResource.getManagementPermissions interface. Does anyone have similar problems?
I also don't see a new client "admin-permissions" in the master realm or database as described in the upgrade guide.
Would it be necessary to use this client as keycloak.client-id when starting the config-cli?
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.
Uh oh!
There was an error while loading. Please reload this page.
-
After upgrading to Keycloak 26.2, we disabled the feature “admin-fine-grained-authz:v1” according to the upgrade guide to switch to the default version v2.
For the automated configuration we use the Adorsys keycloak-config-cli (version 6.4.0). When the configuration is imported, this breaks in Keycloak with the error message:
V1 is probably still expected at the ClientResource.getManagementPermissions interface. Does anyone have similar problems?
I also don't see a new client "admin-permissions" in the master realm or database as described in the upgrade guide.
Would it be necessary to use this client as keycloak.client-id when starting the config-cli?
Beta Was this translation helpful? Give feedback.
All reactions