Update release notes and migration guide for WildFly 25 upgrade

This commit is contained in:
stianst 2021-12-17 10:06:20 +01:00 committed by Stian Thorgersen
parent 2c722b045a
commit 09cbe79b70
3 changed files with 17 additions and 0 deletions

View file

@ -4,6 +4,8 @@
Keycloak server was upgraded to use Wildfly 25.0.1.Final as the underlying container. Keycloak server was upgraded to use Wildfly 25.0.1.Final as the underlying container.
WildFly 25 drops support for the legacy security subsystem, which is being replaced fully by Elytron. This requires significant changes to how Keycloak is configured. Please, refer to the migration guide for more details.
== Upgrade to Quarkus 2.5.3 == Upgrade to Quarkus 2.5.3
Keycloak.X Quarkus preview distribution was upgraded to Quarkus 2.5.3. Keycloak.X Quarkus preview distribution was upgraded to Quarkus 2.5.3.

View file

@ -164,4 +164,5 @@ The resulting element, `server name="default-server"`, which is a child element
</subsystem> </subsystem>
---- ----
For more information on configuring TLS refer to the https://docs.wildfly.org/25/WildFly_Elytron_Security.html#configure-ssltls[WildFly documentation].

View file

@ -2,6 +2,20 @@
=== Migrating to 16.0.0 === Migrating to 16.0.0
==== WildFly 25 upgrade
WildFly 25 deprecates the legacy security subsystem that among other things was used to configure TLS. Due to the amount of changes we are not able to provide migration scripts as we have done in the past.
We recommend that rather than copying configuration files from previous versions of Keycloak that you start with the default configuration files provided in Keycloak 16 and apply the relevant changes.
Configuration for the Keycloak subsystem can be copied directly.
For more information around the Elytron subsystem refer to the https://docs.wildfly.org/25/WildFly_Elytron_Security.html[WildFly documentation].
We are really sorry for this inconvenience and understand this will make it significantly harder for everyone to upgrade to Keycloak 16, but we simply have not been able to find an alternative approach.
One thing worth pointing out is the switch to Quarkus distribution, which we plan to make fully supported in Keycloak 17, will make it significantly easier to configure and upgrade Keycloak.
==== Proxy environment variables ==== Proxy environment variables
{project_name} now respects the standard `HTTP_PROXY`, `HTTPS_PROXY` and `NO_PROXY` environment variables for outgoing {project_name} now respects the standard `HTTP_PROXY`, `HTTPS_PROXY` and `NO_PROXY` environment variables for outgoing