Keycloak 27’s planned removals put two V1 features on the migration list
The upstream project plans to remove Fine-Grained Admin Permissions V1 and Token Exchange V1, and is asking users to flag what still blocks a move to V2.
What changed
The upstream Keycloak project announced on November 19 that it plans to remove Fine-Grained Admin Permissions V1 and Token Exchange V1 in Keycloak 27. The second removal follows from the first: Token Exchange V1 depends on the V1 permissions model. Fine-Grained Admin Permissions V2 and Standard Token Exchange V2 have been the default, supported versions since Keycloak 26.2. This is a plan for the next major release, not an announcement that Keycloak 27 has shipped.
Who it affects
Teams still using either V1 feature should check their upgrade plans now. Keycloak says there is no automatic migration for V1 admin permissions. The project is still working to close gaps in V2, including delegated-admin visibility for members of LDAP-mapped groups and permission handling for child groups. Those are planned improvements, not capabilities the announcement says have already landed.
What to do
Before upgrading to 27, identify realms using V1 admin permissions and clients relying on V1 token exchange. Use the Keycloak upgrading guide to plan the manual permissions transition, and test your delegated-admin and token-exchange workflows against their V2 replacements. If an existing workflow cannot move, the project is asking users to report migration blockers while it can still assess them for the major release.
sources
- Keycloak: Planned Removal of Fine-Grained Admin Permissions V1 in Keycloak 27www.keycloak.org
- Keycloak upgrading guide: Migrating to 26.2.0www.keycloak.org
comments · 0