Repository navigation
Replies: 2 comments 1 reply
|
I've verified that this only affects child groups. If you remove the UUID of the parent from the URI it works: -http://keycloak-ui/admin/master/console/#/example-realm/groups/21f71205-ecf2-4ed3-85c1-e9817a6a69a5/a1825189-997d-4f5d-b6b0-56807c6f0351
+http://keycloak-ui/admin/master/console/#/example-realm/groups/a1825189-997d-4f5d-b6b0-56807c6f0351That issue is tracked here: https://github.com/keycloak/keycloak-ui/issues/3515 |
1 reply
|
Thanks for the update - that gives me an acceptable workaround by simply changing the structure of our groups for now! |
|
@oleeander @Agh42 There is reason to believe that this is already fixed in the nightly build. It would be a great help if you could try it out and report your results in https://github.com/keycloak/keycloak-ui/issues/3515. Thanks. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
We just upgraded to v 19.0.3 and to the new Admin Console. When I try to edit "Groups -> MyGroup -> Group Details -> Role Mapping", no realm- or client-roles are shown. In our setup we exclusively use groups to assign roles to users.
The assigned roles are still present in the access token when I examine it via "Clients -> MyClient -> Client Scopes -> Evaulate". When I switch back to the v1 Admin Console theme, I can still see and edit all role mappings in my groups.
Is this a known issue? Do I need to do any active migration when moving to the v2 theme?
Theme v1:
Theme v2:
All reactions