Starting with Keycloak 26, the Organizations feature is fully supported.
Client libraries updates
Dedicated release cycle for the client libraries
From this release, some of the Keycloak client libraries will have release cycle independent of the Keycloak server release cycle. The 26.0.0 release may be the last one
when the client libraries are released together with the Keycloak server. But from now on, the client libraries may be released at a different time than the Keycloak server.
It is possible that in the future, some more libraries will be included.
The client libraries are supported with Java 8, so it is possible to use them with the client applications deployed on the older application servers.
Compatibility of the client libraries with the server
Beginning with this release, we are testing and supporting client libraries with the same server version and a few previous major server versions.
For details about supported versions of client libraries with server versions, see the Upgrading Guide.
User sessions persisted by default
Keycloak 25 introduced the feature persistent-user-sessions. With this feature enabled all user sessions are persisted in the database as opposed to the previous behavior where only offline sessions were persisted.
In Keycloak 26, this feature is enabled by default. This means that all user sessions are persisted in the database by default.
It is possible to revert this behavior to the previous state by disabling the feature. Follow the Volatile user sessions section in Configuring distributed caches guide for more details.
There is now a new version (v2) of the keycloak login theme, which provides an improved look and feel, including support for switching automatically to a dark theme based on user preferences.
The previous version (v1) is now deprecated, and will be removed in a future release.
For all new realms, keycloak.v2 will be the default login theme. Also, any existing realm that never explicitly set a login theme will be switched to keycloak.v2.
Highly available multi-site deployments
Keycloak 26 introduces significant improvements to the recommended HA multi-site architecture, most notably:
Keycloak deployments are now able to handle user requests simultaneously in both sites.
Active monitoring of the connectivity between the sites is now required to update the replication between the sites in case of a failure.
The loadbalancer blueprint has been updated to use the AWS Global Accelerator as this avoids prolonged fail-over times caused by DNS caching by clients.
Persistent user sessions are now a requirement of the architecture. Consequently, user sessions will be kept
on Keycloak or Infinispan upgrades.
In the past, regaining access to a Keycloak instance when all admin users were locked out was a challenging and complex process. Recognizing these challenges and aiming to significantly enhance the user experience, Keycloak now offers several straightforward methods to bootstrap a temporary admin account and recover lost admin access.
It is now possible to run the start or start-dev commands with specific options to create a temporary admin account. Additionally, a new dedicated command has been introduced, which allows users to regain admin access without hassle.
The underlying Quarkus support for OpenTelemetry Tracing has been exposed to Keycloak and allows obtaining application traces for better observability.
It helps to find performance bottlenecks, determine the cause of application failures, trace a request through the distributed system, and much more.
The support is in preview mode, and we would be happy to obtain any feedback.
The OpenID for Verifiable Credential Issuance (OID4VCI) is still an experimental feature in Keycloak, but it was greatly improved in this release. You will find significant development and discussions
in the Keycloak OAuth SIG. Anyone from the Keycloak community is welcome to join.
The DPoP (OAuth 2.0 Demonstrating Proof-of-Possession) preview feature has improvements. The DPoP is now supported for all grant types.
With previous releases, this feature was supported only for the authorization_code grant type. Support also exists for the DPoP token type on the UserInfo endpoint.
GELF support has been deprecated for a while now, and with this release it has been finally removed from Keycloak.
Other log handlers are available and fully supported to be used as a replacement of GELF, for example Syslog. For details
see the Logging guide.
Lightweight access tokens for Admin REST API
Lightweight access tokens can now be used on the admin REST API. The security-admin-console and admin-cli clients are now using lightweight access tokens by default, so “Always Use Lightweight Access Token” and “Full Scope Allowed” are now enabled on these two clients. However, the behavior in the admin console should effectively remain the same. Be cautious if you have made changes to these two clients and if you are using them for other purposes.
Keycloak JavaScript adapter now standalone
Keycloak JavaScript adapter is now a standalone library and is therefore no longer served statically from the Keycloak server. The goal is to de-couple the library from the Keycloak server, so that it can be refactored independently, simplifying the code and making it easier to maintain in the future. Additionally, the library is now free of third-party dependencies, which makes it more lightweight and easier to use in different environments.
For a complete breakdown of the changes consult the Upgrading Guide.
Hostname v1 feature removed
The deprecated hostname v1 feature was removed. This feature was deprecated in Keycloak 25 and replaced by hostname v2. If you are still using this feature, you must migrate to hostname v2. For more details, see the Configuring the hostname (v2) and the initial migration guide.
Automatic redirect from root to relative path
User is automatically redirected to the path where Keycloak is hosted when the http-relative-path property is specified.
It means when the relative path is set to /auth, and the user access localhost:8080/, the page is redirected to localhost:8080/auth.
The same applies to the management interface when the http-management-relative-path or http-relative-path property is specified.
It improves user experience as users no longer need to set the relative path to the URL explicitly.
Persisting revoked access tokens across restarts
In this release, revoked access tokens are written to the database and reloaded when the cluster is restarted by default when using the embedded caches.
The condition based on the client-attribute was added into Client Policies. You can use condition to specify for the clients
with the specified client attribute having a specified value. It is possible to use either an AND or OR condition when evaluating this condition as mentioned in the documentation
for client policies.
It is possible to specify log levels for all available log handlers, such as console, file, or syslog.
The more fine-grained approach provides the ability to control logging over the whole application and be tailored to your needs.
The deprecated proxy option was removed. This option was deprecated in Keycloak 24 and replaced by the proxy-headers option in combination with hostname options as needed. For more details, see using a reverse proxy and the initial migration guide.
Option proxy-trusted-addresses added
The proxy-trusted-addresses can be used when the proxy-headers option is set to specify a allowlist of trusted proxy addresses. If the proxy address for a given request is not trusted, then the respective proxy header values will not be used.
Option proxy-protocol-enabled added
The proxy-protocol-enabled option controls whether the server should use the HA PROXY protocol when serving requests from behind a proxy. When set to true, the remote address returned will be the one from the actual connecting client.
Option to reload trust and key material added
The https-certificates-reload-period option can be set to define the reloading period of key store, trust store, and certificate files referenced by https-* options. Use -1 to disable reloading. Defaults to 1h (one hour).
Options to configure cache max-count added
The --cache-embedded-${CACHE_NAME}-max-count= can be set to define an upper bound on the number of cache entries in the specified cache.
The https-trust-store-* options have been undeprecated
Based on the community feedback, we decided to undeprecate https-trust-store-* options to allow better granularity in trusted certificates.
The java-keystore key provider supports more algorithms and vault secrets
The java-keystore key provider, which allows loading a realm key from an external java keystore file, has been modified to manage all Keycloak algorithms. Besides, the keystore and key secrets, needed to retrieve the actual key from the store, can be configured using the vault. Therefore a Keycloak realm can externalize any key to the encrypted file without sensitive data stored in the database.
Adding support for ECDH-ES encryption key management algorithms
Now Keycloak allows configuring ECDH-ES, ECDH-ES+A128KW, ECDH-ES+A192KW or ECDH-ES+A256KW as the encryption key management algorithm for clients. The Key Agreement with Elliptic Curve Diffie-Hellman Ephemeral Static (ECDH-ES) specification introduces three new header parameters for the JWT: epk, apu and apv. Currently Keycloak implementation only manages the compulsory epk while the other two (which are optional) are never added to the header. For more information about those algorithms please refer to the JSON Web Algorithms (JWA).
Also, a new key provider, ecdh-generated, is available to generate realm keys and support for ECDH algorithms is added into the Java KeyStore provider.
Support for multiple instances of a social broker in a realm
It is now possible to have multiple instances of the same social broker in a realm.
Most of the time a realm does not need multiple instances of the same social broker. But due to the introduction
of the organization feature, it should be possible to link different instances of the same social broker
to different organizations.
When creating a social broker, you should now provide an Alias and optionally a Display name just like any other
broker.
New generalized event types for credentials
There are now generalized events for updating (UPDATE_CREDENTIAL) and removing (REMOVE_CREDENTIAL) a credential. The credential type is described in the credential_type attribute of the events. The new event types are supported by the Email Event Listener.
The following event types are now deprecated and will be removed in a future version: UPDATE_PASSWORD, UPDATE_PASSWORD_ERROR, UPDATE_TOTP, UPDATE_TOTP_ERROR, REMOVE_TOTP, REMOVE_TOTP_ERROR
Customizable Footer in login Themes
The template.ftl file in the base/login and the keycloak.v2/login theme now allows to customize the footer
of the login box. This can be used to show common links or include custom scripts at the end of the page.
The new footer.ftl template provides a content macro that is rendered at the bottom of the "login box".
Keycloak CR supports standard scheduling options
The Keycloak CR now exposes first class properties for controlling the scheduling of your Keycloak Pods.
Infinispan marshalling changes to Infinispan Protostream
Marshalling is the process of converting Java objects into bytes to send them across the network between Keycloak servers.
With Keycloak 26, we changed the marshalling format from JBoss Marshalling to Infinispan Protostream.
Warning
JBoss Marshalling and Infinispan Protostream are not compatible with each other and incorrect usage may lead to data loss.
Consequently, all caches are cleared when upgrading to this version.
Infinispan Protostream is based on Protocol Buffers (proto 3), which has the advantage of backwards/forwards compatibility.
Removal of OSGi metadata
Since all of the Java adapters that used OSGi metadata have been removed we have stopped generating OSGi metadata for our jars.
Group-related events no longer fired when removing a realm
With the goal of improving the scalability of groups, they are now removed directly from the database when removing a realm.
As a consequence, group-related events like the GroupRemovedEvent are no longer fired when removing a realm.
Identity Providers no longer available from the realm representation
As part of the improvements around the scalability of realms and organizations when they have many identity providers, the realm representation
no longer holds the list of identity providers. However, they are still available from the realm representation
when exporting a realm.
Securing Applications documentation converted into the guide format
The Securing Applications and Services documentation was converted into the new format similar to the Server Installation and Configuration documentation converted in the previous releases.
The documentation is now available under Keycloak Guides.
Removal of legacy cookies
Keycloak no longer sends _LEGACY cookies, which where introduced as a work-around to older browsers not supporting
the SameSite flag on cookies.
The _LEGACY cookies also served another purpose, which was to allow login from an insecure context. Although, this is
not recommended at all in production deployments of Keycloak, it is fairly frequent to access Keycloak over http outside
of localhost. As an alternative to the _LEGACY cookies Keycloak now doesn’t set the secure flag and sets SameSite=Lax
instead of SameSite=None when it detects an insecure context is used.
Property origin in the UserRepresentation is deprecated
The origin property in the UserRepresentation is deprecated and planned to be removed in future releases.
Instead, prefer using the federationLink property to obtain the provider to which a user is linked with.
Upgrading
Before upgrading refer to the migration guide for a complete list of changes.
All resolved issues
Deprecated features
#600 De-couple quickstarts from statically served Keycloak JS quickstarts
New features
#20342 Duplicate groups in the admin console of Keycloak admin/ui
#26178 Support dark mode, at least for the login pages login/ui
#29324 Bootstrapping an admin user using a dedicated command dist/quarkus
#29755 Support AES and HMAC Key-Imports for the JavaKeystoreKeyProvider
#30002 Bootstrapping an admin service account using a dedicated command dist/quarkus
#30009 Warnings for temporary admin user and service account core
#30011 Document admin bootstrapping and recovery docs
#30682 Group assignment: Display disabled information from user admin/ui
#30795 Initiate create events if ClientScopes are created
#31421 Add Events for Organization Creation and Member Assignment organizations
#31642 Include organization attributes and information in ID and access tokens organizations
#31643 Implement invitation-only self-registration for realm users organizations
#32030 Retry remote cache operations with back off
#32135 Option to specify trusted proxies dist/quarkus
#32553 Expose Password Policies in FreeMarker Context for Login Themes
Enhancements
#583 Update dependency on keycloak-client in main branch to 999.0.0-SNAPSHOT quickstarts
#10114 Specific events for webauthn register authentication/webauthn
#30346 Enhance masking around config-keystore dist/quarkus
#30419 Credential Issuer Metadata: Support Optional ```claims``` Object in ```credential_configurations_supported``` in ```openid-credential-issuer``` endpoint oid4vc
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: frontend/package-lock.json
ERROR: npm v10.8.2 is known not to run on Node.js v14.21.3. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
ERROR:
/opt/containerbase/tools/npm/10.8.2/14.21.3/node_modules/npm/lib/utils/error-message.js:11
er.message &&= replaceInfo(er.message)
^^^
SyntaxError: Unexpected token '&&='
at wrapSafe (internal/modules/cjs/loader.js:1029:16)
at Module._compile (internal/modules/cjs/loader.js:1078:27)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1143:10)
at Module.load (internal/modules/cjs/loader.js:979:32)
at Function.Module._load (internal/modules/cjs/loader.js:819:12)
at Module.require (internal/modules/cjs/loader.js:1003:19)
at require (internal/modules/cjs/helpers.js:107:18)
at Object.<anonymous> (/opt/containerbase/tools/npm/10.8.2/14.21.3/node_modules/npm/lib/cli/exit-handler.js:2:48)
at Module._compile (internal/modules/cjs/loader.js:1114:14)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1143:10)
Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 26.x releases. But if you manually upgrade to 26.x then Renovate will re-enable minor and patch updates automatically.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.
This PR contains the following updates:
21.1.2->26.0.4Release Notes
keycloak/keycloak (keycloak-js)
### [`v26.0.4`](https://redirect.github.com/keycloak/keycloak/releases/tag/26.0.4) [Compare Source](https://redirect.github.com/keycloak/keycloak/compare/26.0.2...26.0.4)Upgrading
Before upgrading refer to the migration guide for a complete list of changes.
All resolved issues
Enhancements
admin/client-javaBugs
adapter/javascriptauthenticationdist/quarkusadmin/apidist/quarkuslogin/uildapldapinfinispanldapUpgrading
Before upgrading refer to the migration guide for a complete list of changes.
All resolved issues
Enhancements
dist/quarkusBugs
adapter/javascriptadapter/javascriptadapter/javascriptadmin/uiadmin/apiidentity-brokeringauthentication/webauthndocsdist/quarkusadmin/uidocsdocsadmin/uilogin/uiorganizationsuser-profileorganizationsciimport-exportlogin/uidist/quarkusUpgrading
Before upgrading refer to the migration guide for a complete list of changes.
All resolved issues
Enhancements
operatorstorageBugs
adapter/javascriptauthorization-servicesauthenticationldapadmin/uilogin/uiadmin/uioidcoidcdocsciaccount/uidocsimport-exportdocsdist/quarkuslogin/uiadapter/javascriptorganizationsaccount/uiauthenticationorganizationscoreauthenticationinfinispanauthenticationadmin/uiadmin/uiHighlights
Organizations supported
Starting with Keycloak 26, the Organizations feature is fully supported.
Client libraries updates
Dedicated release cycle for the client libraries
From this release, some of the Keycloak client libraries will have release cycle independent of the Keycloak server release cycle. The 26.0.0 release may be the last one when the client libraries are released together with the Keycloak server. But from now on, the client libraries may be released at a different time than the Keycloak server.
The client libraries are these artifacts:
Java admin client - Maven artifact
org.keycloak:keycloak-admin-clientJava authorization client - Maven artifact
org.keycloak:keycloak-authz-clientJava policy enforcer - Maven artifact
org.keycloak:keycloak-policy-enforcerIt is possible that in the future, some more libraries will be included.
The client libraries are supported with Java 8, so it is possible to use them with the client applications deployed on the older application servers.
Compatibility of the client libraries with the server
Beginning with this release, we are testing and supporting client libraries with the same server version and a few previous major server versions.
For details about supported versions of client libraries with server versions, see the Upgrading Guide.
User sessions persisted by default
Keycloak 25 introduced the feature
persistent-user-sessions. With this feature enabled all user sessions are persisted in the database as opposed to the previous behavior where only offline sessions were persisted. In Keycloak 26, this feature is enabled by default. This means that all user sessions are persisted in the database by default.It is possible to revert this behavior to the previous state by disabling the feature. Follow the
Volatile user sessionssection in Configuring distributed caches guide for more details.For information on how to upgrade, see the Upgrading Guide.
New default login theme
There is now a new version (
v2) of thekeycloaklogin theme, which provides an improved look and feel, including support for switching automatically to a dark theme based on user preferences.The previous version (
v1) is now deprecated, and will be removed in a future release.For all new realms,
keycloak.v2will be the default login theme. Also, any existing realm that never explicitly set a login theme will be switched tokeycloak.v2.Highly available multi-site deployments
Keycloak 26 introduces significant improvements to the recommended HA multi-site architecture, most notably:
Keycloak deployments are now able to handle user requests simultaneously in both sites.
Active monitoring of the connectivity between the sites is now required to update the replication between the sites in case of a failure.
The loadbalancer blueprint has been updated to use the AWS Global Accelerator as this avoids prolonged fail-over times caused by DNS caching by clients.
Persistent user sessions are now a requirement of the architecture. Consequently, user sessions will be kept on Keycloak or Infinispan upgrades.
For information on how to migrate, see the Upgrading Guide.
Admin Bootstrapping and Recovery
In the past, regaining access to a Keycloak instance when all admin users were locked out was a challenging and complex process. Recognizing these challenges and aiming to significantly enhance the user experience, Keycloak now offers several straightforward methods to bootstrap a temporary admin account and recover lost admin access.
It is now possible to run the
startorstart-devcommands with specific options to create a temporary admin account. Additionally, a new dedicated command has been introduced, which allows users to regain admin access without hassle.For detailed instructions and more information on this topic, refer to the Admin Bootstrap and Recovery guide.
OpenTelemetry Tracing preview
The underlying Quarkus support for OpenTelemetry Tracing has been exposed to Keycloak and allows obtaining application traces for better observability. It helps to find performance bottlenecks, determine the cause of application failures, trace a request through the distributed system, and much more. The support is in preview mode, and we would be happy to obtain any feedback.
For more information, see the Enabling Tracing guide.
OpenID for Verifiable Credential Issuance
The OpenID for Verifiable Credential Issuance (OID4VCI) is still an experimental feature in Keycloak, but it was greatly improved in this release. You will find significant development and discussions in the Keycloak OAuth SIG. Anyone from the Keycloak community is welcome to join.
Many thanks to all members of the OAuth SIG group for the participation on the development and discussions about this feature. Especially thanks to the Francis Pouatcha, Pascal Knüppel, Takashi Norimatsu, Ingrid Kamga, Stefan Wiedemann and Thomas Darimont
DPoP improvements
The DPoP (OAuth 2.0 Demonstrating Proof-of-Possession) preview feature has improvements. The DPoP is now supported for all grant types. With previous releases, this feature was supported only for the
authorization_codegrant type. Support also exists for the DPoP token type on the UserInfo endpoint.Many thanks to Pascal Knüppel for the contribution.
Removal of GELF logging handler
GELF support has been deprecated for a while now, and with this release it has been finally removed from Keycloak. Other log handlers are available and fully supported to be used as a replacement of GELF, for example Syslog. For details see the Logging guide.
Lightweight access tokens for Admin REST API
Lightweight access tokens can now be used on the admin REST API. The
security-admin-consoleandadmin-cliclients are now using lightweight access tokens by default, so “Always Use Lightweight Access Token” and “Full Scope Allowed” are now enabled on these two clients. However, the behavior in the admin console should effectively remain the same. Be cautious if you have made changes to these two clients and if you are using them for other purposes.Keycloak JavaScript adapter now standalone
Keycloak JavaScript adapter is now a standalone library and is therefore no longer served statically from the Keycloak server. The goal is to de-couple the library from the Keycloak server, so that it can be refactored independently, simplifying the code and making it easier to maintain in the future. Additionally, the library is now free of third-party dependencies, which makes it more lightweight and easier to use in different environments.
For a complete breakdown of the changes consult the Upgrading Guide.
Hostname v1 feature removed
The deprecated hostname v1 feature was removed. This feature was deprecated in Keycloak 25 and replaced by hostname v2. If you are still using this feature, you must migrate to hostname v2. For more details, see the Configuring the hostname (v2) and the initial migration guide.
Automatic redirect from root to relative path
User is automatically redirected to the path where Keycloak is hosted when the
http-relative-pathproperty is specified. It means when the relative path is set to/auth, and the user accesslocalhost:8080/, the page is redirected tolocalhost:8080/auth.The same applies to the management interface when the
http-management-relative-pathorhttp-relative-pathproperty is specified.It improves user experience as users no longer need to set the relative path to the URL explicitly.
Persisting revoked access tokens across restarts
In this release, revoked access tokens are written to the database and reloaded when the cluster is restarted by default when using the embedded caches.
For information on how to migrate, see the Upgrading Guide.
Client Attribute condition in Client Policies
The condition based on the client-attribute was added into Client Policies. You can use condition to specify for the clients with the specified client attribute having a specified value. It is possible to use either an AND or OR condition when evaluating this condition as mentioned in the documentation for client policies.
Many thanks to Yoshiyuki Tabata for the contribution.
Specify different log levels for log handlers
It is possible to specify log levels for all available log handlers, such as
console,file, orsyslog. The more fine-grained approach provides the ability to control logging over the whole application and be tailored to your needs.For more information, see the Logging guide.
Proxy option removed
The deprecated
proxyoption was removed. This option was deprecated in Keycloak 24 and replaced by theproxy-headersoption in combination with hostname options as needed. For more details, see using a reverse proxy and the initial migration guide.Option
proxy-trusted-addressesaddedThe
proxy-trusted-addressescan be used when theproxy-headersoption is set to specify a allowlist of trusted proxy addresses. If the proxy address for a given request is not trusted, then the respective proxy header values will not be used.Option
proxy-protocol-enabledaddedThe
proxy-protocol-enabledoption controls whether the server should use the HA PROXY protocol when serving requests from behind a proxy. When set to true, the remote address returned will be the one from the actual connecting client.Option to reload trust and key material added
The
https-certificates-reload-periodoption can be set to define the reloading period of key store, trust store, and certificate files referenced by https-* options. Use -1 to disable reloading. Defaults to 1h (one hour).Options to configure cache max-count added
The
--cache-embedded-${CACHE_NAME}-max-count=can be set to define an upper bound on the number of cache entries in the specified cache.The
https-trust-store-*options have been undeprecatedBased on the community feedback, we decided to undeprecate
https-trust-store-*options to allow better granularity in trusted certificates.The
java-keystorekey provider supports more algorithms and vault secretsThe
java-keystorekey provider, which allows loading a realm key from an external java keystore file, has been modified to manage all Keycloak algorithms. Besides, the keystore and key secrets, needed to retrieve the actual key from the store, can be configured using the vault. Therefore a Keycloak realm can externalize any key to the encrypted file without sensitive data stored in the database.For more information about this subject, see Configuring realm keys.
Adding support for ECDH-ES encryption key management algorithms
Now Keycloak allows configuring ECDH-ES, ECDH-ES+A128KW, ECDH-ES+A192KW or ECDH-ES+A256KW as the encryption key management algorithm for clients. The Key Agreement with Elliptic Curve Diffie-Hellman Ephemeral Static (ECDH-ES) specification introduces three new header parameters for the JWT:
epk,apuandapv. Currently Keycloak implementation only manages the compulsoryepkwhile the other two (which are optional) are never added to the header. For more information about those algorithms please refer to the JSON Web Algorithms (JWA).Also, a new key provider,
ecdh-generated, is available to generate realm keys and support for ECDH algorithms is added into the Java KeyStore provider.Many thanks to Justin Tay for the contribution.
Support for multiple instances of a social broker in a realm
It is now possible to have multiple instances of the same social broker in a realm.
Most of the time a realm does not need multiple instances of the same social broker. But due to the introduction of the
organizationfeature, it should be possible to link different instances of the same social broker to different organizations.When creating a social broker, you should now provide an
Aliasand optionally aDisplay namejust like any other broker.New generalized event types for credentials
There are now generalized events for updating (
UPDATE_CREDENTIAL) and removing (REMOVE_CREDENTIAL) a credential. The credential type is described in thecredential_typeattribute of the events. The new event types are supported by the Email Event Listener.The following event types are now deprecated and will be removed in a future version:
UPDATE_PASSWORD,UPDATE_PASSWORD_ERROR,UPDATE_TOTP,UPDATE_TOTP_ERROR,REMOVE_TOTP,REMOVE_TOTP_ERRORCustomizable Footer in login Themes
The
template.ftlfile in thebase/loginand thekeycloak.v2/logintheme now allows to customize the footer of the login box. This can be used to show common links or include custom scripts at the end of the page.The new
footer.ftltemplate provides acontentmacro that is rendered at the bottom of the "login box".Keycloak CR supports standard scheduling options
The Keycloak CR now exposes first class properties for controlling the scheduling of your Keycloak Pods.
For more details, see the Operator Advanced Configuration.
KeycloakRealmImport CR supports placeholder replacement
The KeycloakRealmImport CR now exposes
spec.placeholdersto create environment variables for placeholder replacement in the import.For more details, see the Operator Realm Import.
Configuring the LDAP Connection Pool
In this release, the LDAP connection pool configuration relies solely on system properties.
For more details, see Configuring the connection pool.
Infinispan marshalling changes to Infinispan Protostream
Marshalling is the process of converting Java objects into bytes to send them across the network between Keycloak servers. With Keycloak 26, we changed the marshalling format from JBoss Marshalling to Infinispan Protostream.
Infinispan Protostream is based on Protocol Buffers (proto 3), which has the advantage of backwards/forwards compatibility.
Removal of OSGi metadata
Since all of the Java adapters that used OSGi metadata have been removed we have stopped generating OSGi metadata for our jars.
Group-related events no longer fired when removing a realm
With the goal of improving the scalability of groups, they are now removed directly from the database when removing a realm. As a consequence, group-related events like the
GroupRemovedEventare no longer fired when removing a realm.For information on how to migrate, see the Upgrading Guide.
Identity Providers no longer available from the realm representation
As part of the improvements around the scalability of realms and organizations when they have many identity providers, the realm representation no longer holds the list of identity providers. However, they are still available from the realm representation when exporting a realm.
For information on how to migrate, see the Upgrading Guide.
Securing Applications documentation converted into the guide format
The Securing Applications and Services documentation was converted into the new format similar to the Server Installation and Configuration documentation converted in the previous releases. The documentation is now available under Keycloak Guides.
Removal of legacy cookies
Keycloak no longer sends
_LEGACYcookies, which where introduced as a work-around to older browsers not supporting theSameSiteflag on cookies.The
_LEGACYcookies also served another purpose, which was to allow login from an insecure context. Although, this is not recommended at all in production deployments of Keycloak, it is fairly frequent to access Keycloak overhttpoutside oflocalhost. As an alternative to the_LEGACYcookies Keycloak now doesn’t set thesecureflag and setsSameSite=Laxinstead ofSameSite=Nonewhen it detects an insecure context is used.Property
originin theUserRepresentationis deprecatedThe
originproperty in theUserRepresentationis deprecated and planned to be removed in future releases.Instead, prefer using the
federationLinkproperty to obtain the provider to which a user is linked with.Upgrading
Before upgrading refer to the migration guide for a complete list of changes.
All resolved issues
Deprecated features
quickstartsNew features
admin/uilogin/uidist/quarkusdist/quarkuscoredocsadmin/uiorganizationsorganizationsorganizationsdist/quarkusEnhancements
quickstartsauthentication/webauthnadapter/javascriptcoreoidcaccount/uilogin/uiadmin/clioidcoidcdist/quarkuswelcome/uidist/quarkusadapter/javascriptdist/quarkusoperatordocsdocsimport-exportoperatorstoragesamloid4vclogin/uidist/quarkusoperatordist/quarkusoperatoradmin/apiorganizationsorganizationsdist/quarkusoid4vcdist/quarkusoid4vcdocscoreadmin/client-javaadmin/client-javaauthenticationorganizationsorganizationsorganizationsadmin/client-jsdocsoid4vccoreoid4vcoid4vcoperatoroid4vcorganizationsauthorization-servicesoidcoidcadmin/uiThanks for the PR!
Deployments, as required, will be available below:
Please create PRs in draft mode. Mark as ready to enable:
After merge, new images are deployed in:
⚠️ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below:
File name: frontend/package-lock.json
Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future
26.xreleases. But if you manually upgrade to26.xthen Renovate will re-enableminorandpatchupdates automatically.If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.