Skip to content
senn-techsenn-tech
Back to blog
Infrastructure
Servers, Proxmox and network2026-11-20· By Franz Senn

Keycloak 27 is set to drop FGAP V1 and Legacy Token Exchange

On 19 Nov 2026 the Keycloak project announced on its official blog that it plans to remove two features with version 27: the first version of Fine-Grained Admin Permissions (FGAP V1) and Legacy Token Exchange, which depends on it. On 20 Nov 2026 we checked our two Keycloak instances to see whether we are affected. Result: no. The check we used is described below and works on any instance.

Logo of Keycloak
Keycloak is the identity and access management behind our internal sign-ins. The announcement comes from the official project blog of 19 Nov 2026, the inventory figures from our own read-only measurement on 20 Nov 2026. (Quelle: Simple Icons 16.36.0, file keycloak.svg (license field in the metadata: custom, Linux Foundation Trademark Usage), trademark: Keycloak Authors / The Linux Foundation)

Fine-Grained Admin Permissions (FGAP) let you delegate Keycloak's admin console piece by piece: a person may, for example, create users in one area or edit only certain clients, without seeing realm administration. Version 2 of the model has been the default since Keycloak 26.2 of 11 April 2025. Version 1 stayed a preview that has to be switched on at startup. Legacy Token Exchange is the old preview implementation of token exchange and needs FGAP V1 for its permissions.

What the vendor wrote

The post of 19 Nov 2026 names two linked tracks. FGAP V1 is to go in Keycloak 27, and because Token Exchange V1 depends on it, its removal is announced along with it. Before that the team wants to close known gaps between V1 and V2: delegated admins should be able to see users who also belong to groups delegated to other admins, the visibility of group members through LDAP group mappers should work, group permissions get a level for subgroups, and the group resource type gets the scope map-roles-members. Anyone using V1 who is blocked from switching should say so in the tracking issue.

The post asks for feedback and sets no deadline. The ticket shows the same: issue 44122 is titled "Remove Fine-Grained Admin Permissions v1", has been open since 11 Nov 2025, sits under the milestone 27.0 Release and has four comments, two of them from 20 Nov 2026.

Why Legacy Token Exchange goes with it

Since 26.2 the Keycloak documentation distinguishes two implementations: Standard Token Exchange as the feature token-exchange-standard:v2, enabled by default and officially supported, and Legacy Token Exchange as the feature token-exchange:v1, still a preview. For Legacy the rule is: if you need it, you also need FGAP V1, because FGAP V2 has no token exchange permissions. The documentation reasons that token exchange is conceptually not an admin permission. Exchanging an external token for an internal one is, per the docs, implemented only in Legacy.

In operation that means: an instance that built delegated administration on V1 and enabled Legacy Token Exchange for a gateway case loses both in Keycloak 27 at the same time.

The schedule, as measured in the tickets

Keycloak 27 does not exist yet. The project's release list shows 26.8.2 of 5 Nov 2026 as the newest version, and there is no tag 27.0.0 (both retrieved from the GitHub API on 20 Nov 2026). The milestones in the tracker carry dates: the development milestone 27.0 is set to 29 January 2027 with 90 open items, the milestone 27.0 Release to 31 March 2027 with 138 open items. A milestone date is a plan and no promise, but it is the only figure available for the timeframe. In the issue itself, a reply to a question of 20 Nov 2026 says the list of changes for version 27 is not final.

What migrating means in practice

The upgrade documentation for 26.2.0 states that, because of the fundamental change in the permission model, there is no automatic migration from V1 to V2. When you enable it, Keycloak creates a new client admin-permissions that holds the V2 model. The V1 model stays in the existing client realm-management. Administrators have to recreate permissions and policies in the new model, in the "Permissions" section of the admin console or through the admin REST API. According to the docs, the "user-impersonated" permission and the client permission "configure" are removed, and every permission has to be granted its operations individually.

The effort follows the number of policies. The usual order for an identity rebuild makes sense: realm export and backup first, write down the existing delegation as a list, rebuild it in a copy, then check with a real delegated account that it can still do the same things and nothing else.

Rebuilding FGAP V1 as V2 per the upgrade docs: no automationSecure the staterealm export and databasedump before any changeEnable V2Admin Permissions switch inrealm settingsClientadmin-permissionsKeycloak creates it onenablingRecreate policiesno automatic migration,every delegation by handVerifywith a real delegatedaccount: same thingsallowed, nothing else
The V1 model stays in its existing management client, the V2 model goes into the new admin-permissions client. Highlighted are the steps nobody does for you. (Quelle: Keycloak, upgrade changes for 26.2.0)

What we measured on our two instances

We run two Keycloak instances: one for the home network, one for the company. On both we looked read-only on 20 Nov 2026 around 05:20 UTC, using docker inspect, the jar file name and SQL queries against the matching PostgreSQL.

CheckUnitHome instanceCompany instance
Built-in server version, measured from the jar file nameversion26.8.226.8.2
Image tag of the containerversion26.8.226.8.2
Resource servers for permission modelscount00
Policies in resource_server_policycount00
Client admin-permissions (V2 model)present?nono
Realm flag adminPermissionsEnabledvaluenot setfalse
Feature switches at startup (--features, environment, keycloak.conf)count00

Counted on 20 Nov 2026, the method is in the sources section. Both instances run 26.8.2, the newest release. The all-clear rests on the zero rows: neither instance has resource servers or policies, so neither a V1 nor a V2 permission model exists, and the V2 client was never created. No feature switch is set at startup, so neither V1 nor Legacy Token Exchange was enabled. For us the removal in Keycloak 27 is one line in the changelog.

You would be affected by a different route: if the sign-in of a site's machines hangs on this service, a botched upgrade takes the whole site down. For running Keycloak see Keycloak as central sign-in, for the latest security fixes Keycloak 26.7.5 and 26.8.0.

How to check your instance

  1. Read the version from the running system instead of trusting the tag: docker exec <container> /opt/keycloak/bin/kc.sh --version, cross-check with the jar file name under /opt/keycloak/lib/lib/main/. The image tag describes the pulled image, the jar name describes what is running.
  2. Look at the feature switches: search Config.Env and Config.Args from docker inspect <container> for features, plus /opt/keycloak/conf/keycloak.conf. No hit means admin-fine-grained-authz:v1 and token-exchange:v1 are not enabled by a switch.
  3. Read the realm state: look at the "Admin Permissions" switch in the realm settings, or call GET /admin/realms/<realm> and watch adminPermissionsEnabled. If a client admin-permissions also exists, V2 is in use.
  4. Without admin rights, count in the database: select count(*) from resource_server; and select count(*) from resource_server_policy;. Two zeros rule out both permission models.
  5. Classify token exchange: Standard Token Exchange needs a switch on the individual client and not token-exchange:v1. If the feature token-exchange is not set, no client can use Legacy Token Exchange.

Before any major-version upgrade, put a database dump and a realm export in front of the change, plus a trial run on a copy. If you would rather not plan such a rebuild alone, our IT support page lists what we offer, and the posts from the same area are under Servers and network.

What we do not claim

We have not tested an upgrade to Keycloak 27, because that version does not exist. What is measured is the state of 26.8.2 and the milestone list. We have not checked the V1 interface, because nothing migratable is configured on either instance. The gap closures named are announcements and the milestone dates are planning: 138 open items in the release milestone can slip.

Further Reading

Own measurement: read-only SSH access to both Keycloak hosts on 20 Nov 2026 around 05:20 UTC. docker ps and docker inspect for image and startup parameters, ls /opt/keycloak/lib/lib/main/ for the jar name, grep -i feature /opt/keycloak/conf/keycloak.conf, then SQL queries against the database containers (tables realm, client, realm_attribute, resource_server, resource_server_policy). No change to configuration, database or operation. The public figures were retrieved on 20 Nov 2026.

Questions?
Do I have to prepare anything before upgrading to Keycloak 27?+

Only if the instance uses Fine-Grained Admin Permissions V1. Since Keycloak 26.2, V1 has to be switched on explicitly with `--features=admin-fine-grained-authz:v1`. If you are unsure, count in the database how many resource servers and policies exist. If both are zero there is nothing to migrate, and the normal upgrade path with a database backup applies.

Is regular token exchange affected too?+

No. What is planned for removal is the old preview version `token-exchange:v1` (legacy). Standard Token Exchange (`token-exchange-standard:v2`) has been the default since 26.2 and stays. The coupling is that Legacy Token Exchange does not work without FGAP V1, because FGAP V2 deliberately has no token exchange permissions.

Did the announcement come out of the blue?+

The tracking issue for the removal has been open since 11 Nov 2025 under the milestone 27.0 Release. What is new is the public call of 19 Nov 2026 to report blocking cases before anything is removed. By 20 Nov 2026 the issue had four comments.