Keycloak 25 to 26 upgrade
Moving from Keycloak 25 to 26 without losing sessions: enabling persistent sessions first, the Protostream cache change, hostname v2 and proxy-headers, and testing custom providers against the new release.

Planning Keycloak version upgrades: what changed in the 26 line, how the database migrates, and when rolling updates avoid downtime.
Moving from Keycloak 25 to 26 without losing sessions: enabling persistent sessions first, the Protostream cache change, hostname v2 and proxy-headers, and testing custom providers against the new release.
Keeping a Keycloak 26 deployment current through the quarterly minor releases: reading the per-release migration notes, opt-in breaking changes, and the 26.8 changes to SMTP, logout tokens and multi-site.
Applying Keycloak patch releases without an outage: the update-compatibility check, rolling restarts behind sticky sessions, and the Operator rolling update strategy.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.