Updated documentations to mention Resteasy reactive migration
Closes #23444
This commit is contained in:
parent
0bd2b342d7
commit
7b0683879d
2 changed files with 9 additions and 2 deletions
|
@ -22,4 +22,8 @@ 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].
|
||||
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.
|
||||
|
|
|
@ -135,6 +135,9 @@ Stream<GroupModel> getTopLevelGroupsStream(RealmModel realm,
|
|||
|
||||
Endpoint `GET {keycloak server}/realms/{realm}/groups/{group_id}/children` added as a way to get subgroups of specific groups that support pagination
|
||||
|
||||
= RESTEeasy Reactive
|
||||
Relying on RESTEasy Classic is not longer an option because it is not available anymore. Migration will be needed for SPI's and code that is relying on RESTEasy Classic and related packages part of `org.jboss.resteasy.spi.*`.
|
||||
|
||||
= Partial export requires manage-realm permission
|
||||
|
||||
The endpoint `POST {keycloak server}/realms/{realm}/partial-export` and the corresponding action in the admin console now require `manage-realm` permission for execution instead of `view-realm`. This endpoint exports the realm configuration into a JSON file and the new permission is more appropriate. The parameters `exportGroupsAndRoles` and `exportClients`, which include the realm groups/roles and clients in the export respectively, continue managing the same permissions (`query-groups` and `view-clients`).
|
||||
The endpoint `POST {keycloak server}/realms/{realm}/partial-export` and the corresponding action in the admin console now require `manage-realm` permission for execution instead of `view-realm`. This endpoint exports the realm configuration into a JSON file and the new permission is more appropriate. The parameters `exportGroupsAndRoles` and `exportClients`, which include the realm groups/roles and clients in the export respectively, continue managing the same permissions (`query-groups` and `view-clients`).
|
||||
|
|
Loading…
Reference in a new issue