keycloak-scim/docs/documentation/release_notes/topics/23_0_0.adoc

= Localization files for themes default to UTF-8 encoding

Message properties files for themes are now read in UTF-8 encoding, with an automatic fallback to ISO-8859-1 encoding.

See the migration guide for more details.

= FAPI 2 drafts support

Keycloak has new client profiles `fapi-2-security-profile` and `fapi-2-message-signing`, which ensure Keycloak enforces compliance with
the latest FAPI 2 draft specifications when communicating with your clients. Thanks to https://github.com/tnorimat[Takashi Norimatsu] for the contribution.

= DPoP preview support

Keycloak has preview for support for OAuth 2.0 Demonstrating Proof-of-Possession at the Application Layer (DPoP). Thanks to
https://github.com/tnorimat[Takashi Norimatsu] and https://github.com/dteleguin[Dmitry Telegin] for their contributions.

= Passkeys support

Keycloak has preview support for https://fidoalliance.org/passkeys/[Passkeys].

Passkey registration and authentication are realized by the features of WebAuthn.
Therefore, users of Keycloak can do passkey registration and authentication by existing WebAuthn registraton and authentication.

Both synced passkeys and device-bound passkeys can be used for both Same-Device and Cross-Device Authentication.
However, passkeys operations success depends on the user's environment. Make sure which operations can succeed in https://passkeys.dev/device-support/[the environment].

= RESTEasy Reactive

Keycloak has switched to RESTEasy Reactive. Applications using `quarkus-resteasy-reactive` should still benefit from a better startup time, runtime performance, and memory footprint, even though not using reactive style/semantics. SPI's that depend directly on JAX-RS API should be compatible with this change. SPI's that depend on RESTEasy Classic including `ResteasyClientBuilder` will not be compatible and will require update, this will also be true for other implementation of the JAX-RS API like Jersey.
Use Java mechanisms to read language files and default to UTF-8 (#21755) Closes #21753 2023-08-01 09:27:10 +00:00			`= Localization files for themes default to UTF-8 encoding`

			`Message properties files for themes are now read in UTF-8 encoding, with an automatic fallback to ISO-8859-1 encoding.`

			`See the migration guide for more details.`

Release notes and documentation for FAPI 2 (#22228) Closes #21945 Co-authored-by: andymunro <48995441+andymunro@users.noreply.github.com> 2023-08-04 06:21:27 +00:00			`= FAPI 2 drafts support`

			Keycloak has new client profiles `fapi-2-security-profile` and `fapi-2-message-signing`, which ensure Keycloak enforces compliance with
			`the latest FAPI 2 draft specifications when communicating with your clients. Thanks to https://github.com/tnorimat[Takashi Norimatsu] for the contribution.`

DPoP release notes and documentation polishing closes #21922 2023-08-07 09:28:40 +00:00			`= DPoP preview support`

			`Keycloak has preview for support for OAuth 2.0 Demonstrating Proof-of-Possession at the Application Layer (DPoP). Thanks to`
			`https://github.com/tnorimat[Takashi Norimatsu] and https://github.com/dteleguin[Dmitry Telegin] for their contributions.`
passkeys: documentation closes #23660 2023-10-24 01:31:51 +00:00
			`= Passkeys support`

			`Keycloak has preview support for https://fidoalliance.org/passkeys/[Passkeys].`

			`Passkey registration and authentication are realized by the features of WebAuthn.`
			`Therefore, users of Keycloak can do passkey registration and authentication by existing WebAuthn registraton and authentication.`

			`Both synced passkeys and device-bound passkeys can be used for both Same-Device and Cross-Device Authentication.`
Updated documentations to mention Resteasy reactive migration Closes #23444 2023-10-27 15:53:26 +00:00			`However, passkeys operations success depends on the user's environment. Make sure which operations can succeed in https://passkeys.dev/device-support/[the environment].`

			`= RESTEasy Reactive`

			Keycloak has switched to RESTEasy Reactive. Applications using `quarkus-resteasy-reactive` should still benefit from a better startup time, runtime performance, and memory footprint, even though not using reactive style/semantics. SPI's that depend directly on JAX-RS API should be compatible with this change. SPI's that depend on RESTEasy Classic including `ResteasyClientBuilder` will not be compatible and will require update, this will also be true for other implementation of the JAX-RS API like Jersey.