Keycloak

1
= Highlights
2

3
== Quarkus distribution is now fully supported
4

5
The default Keycloak distribution is now based on Quarkus. The new distribution is faster, leaner, and a lot easier to configure!
6

7
We appreciate migrating from the WildFly distribution is not going to be straightforward for everyone, since how you start and configure Keycloak has radically changed. With that in mind we will continue to support the WildFly distribution until June 2022.
8

9
For information on how to migrate to the new distribution check out the https://www.keycloak.org/migration/migrating-to-quarkus[Quarkus Migration Guide].
10

11
== Quarkus distribution updates
12

13
A lot of effort went into polishing and improving the Quarkus distribution to make it as good as an experience as possible. A few highlights include:
14

15
* A new approach to documentation in form of server guides to help you install and configure Keycloak
16
* Upgraded Quarkus to 2.7.0.Final
17
* Configuration file is no longer Java specific, and aligns configuration keys with CLI arguments
18
* Clearer separation between `build options` and `runtime configuration`.
19
* `h2-mem` and `h2-file` databases renamed to `dev-mem` and `dev-file`.
20
* Simplified enabling and disabling features
21
* Custom, and unsupported, Quarkus configuration is done through `conf/quarkus.properties`.
22
* Ability to add custom Java Options via JAVA_OPTS_APPEND (thanks to https://github.com/dasniko[dasniko])
23
* Initial logging capabilities
24
* Initial support for Cross-DC
25
* User-defined profiles are no longer supported but using different configuration files to achieve the same goal
26
* Quickstarts updated to use the new distribution
27
== Other improvements
28

29
=== Offline sessions lazy loaded
30

31
The offline sessions are now lazily fetched from the database by default instead of preloading during the server startup.
32
To change the default behavior, see link:{adminguide_link}#offline-sessions-preloading[{adminguide_name}].
33

34
=== Improved User Search
35

36
{project_name} now supports a glob-like syntax for the user search when listing users in the Admin Console,
37
which allows for three different types of searches: prefix (`foo*` which became the default search), infix (`\*foo*`), and exact `"foo"`)
38