live wire
▸IDENTITY · Keycloak 27 plans to remove Fine-Grained Admin Permissions V1 and Token Exchange V1Keycloak project▸AI · Inferact tests vLLM pipeline parallelism for prefill, reporting up to 23% more requests per GPU at a 2-second targetInferact Engineering (November 2026)▸SECURITY · Red Hat updates standard OpenJDK 21 RPMs for Hardened Images after earlier portable-package fixRed Hat Product Errata▸PLATFORM · Red Hat Multiarch Tuning 1.4.1 makes pod placement plugins optional and adds a downgrade caveatRed Hat Product Errata▸SECURITY · Red Hat updates OpenJDK 21 RPMs for Hardened Images to fix Java4ShellRed Hat Product Errata▸PLATFORM · Red Hat tests OpenShift Virtualization 4.22 with 10,000 active VMs during upgradesRed Hat Developer▸AI · vLLM adds day-zero support for Thinking Machines’ looped Inkling 2 MinivLLM Blog▸SECURITY · Red Hat rates OpenShift Dev Spaces 3.31.4 a Critical security updateRed Hat Product Errata▸SECURITY · Quarkus tells 3.27 users to switch from UBI 9 1.23 to 1.24 for the Java4Shell fixQuarkus Blog▸SECURITY · Red Hat issues Critical OpenJDK 25.0.5.1 update for WindowsRed Hat Product Errata▸PLATFORM · Red Hat resolves Lightspeed email outage; about 42 customers may miss daily summariesRed Hat Status▸JAVA · Red Hat details how to diagnose HikariCP connection pool stalls on OpenShiftRed Hat Developer▸SUPPLY CHAIN · Red Hat publishes Renovate presets for Lightwell dependency rebuildsRed Hat Developer▸PLATFORM · Red Hat resumes Lightspeed email delivery after outage, warns of delayed notificationsRed Hat Status▸IDENTITY · Keycloak 27 plans to remove Fine-Grained Admin Permissions V1 and Token Exchange V1Keycloak project▸AI · Inferact tests vLLM pipeline parallelism for prefill, reporting up to 23% more requests per GPU at a 2-second targetInferact Engineering (November 2026)▸SECURITY · Red Hat updates standard OpenJDK 21 RPMs for Hardened Images after earlier portable-package fixRed Hat Product Errata▸PLATFORM · Red Hat Multiarch Tuning 1.4.1 makes pod placement plugins optional and adds a downgrade caveatRed Hat Product Errata▸SECURITY · Red Hat updates OpenJDK 21 RPMs for Hardened Images to fix Java4ShellRed Hat Product Errata▸PLATFORM · Red Hat tests OpenShift Virtualization 4.22 with 10,000 active VMs during upgradesRed Hat Developer▸AI · vLLM adds day-zero support for Thinking Machines’ looped Inkling 2 MinivLLM Blog▸SECURITY · Red Hat rates OpenShift Dev Spaces 3.31.4 a Critical security updateRed Hat Product Errata▸SECURITY · Quarkus tells 3.27 users to switch from UBI 9 1.23 to 1.24 for the Java4Shell fixQuarkus Blog▸SECURITY · Red Hat issues Critical OpenJDK 25.0.5.1 update for WindowsRed Hat Product Errata▸PLATFORM · Red Hat resolves Lightspeed email outage; about 42 customers may miss daily summariesRed Hat Status▸JAVA · Red Hat details how to diagnose HikariCP connection pool stalls on OpenShiftRed Hat Developer▸SUPPLY CHAIN · Red Hat publishes Renovate presets for Lightwell dependency rebuildsRed Hat Developer▸PLATFORM · Red Hat resumes Lightspeed email delivery after outage, warns of delayed notificationsRed Hat Status
upstreambeat.ai
releaseIDENTITY

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.

By The Release Desk· Nov 21, 2026the quick take — two AI hosts go live when you do

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.

Filed by The Release Desk. Corrections: desk@upstreambeat.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.