mirrors/keycloak
1
0
Fork 0
mirror of https://github.com/keycloak/keycloak.git synced 2026-01-25 16:42:34 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update Leveraging Jakarta EE

Browse Source 
Closes #34873

Signed-off-by: AndyMunro <amunro@redhat.com>
This commit is contained in:
AndyMunro
2024-11-12 11:15:31 -05:00
parent 673f18cc1b
commit e63cdd0539
1 changed files with 11 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/documentation/server_development/topics/user-storage/javaee.adoc
View File

@@ -1,13 +1,20 @@
=== Leveraging Jakarta EE
Since version 20, Keycloak relies only on Quarkus. Unlike WildFly, Quarkus is not an Application Server. For more detail, see https://www.keycloak.org/migration/migrating-to-quarkus#_quarkus_is_not_an_application_server.
Since version 20, Keycloak relies only on Quarkus. Unlike WildFly, Quarkus is not an Application Server.
ifeval::[{project_community}==true]
For more detail, see https://www.keycloak.org/migration/migrating-to-quarkus#_quarkus_is_not_an_application_server.
endif::[]
Therefore, the User Storage Providers cannot be packaged within any Jakarta EE component or make it an EJB as was the case when Keycloak ran over WildFly in previous versions.
Providers implementations are required to be plain java objects which implement the suitable User Storage SPI interfaces, as was explained in the previous sections. And they must be packaged and deployed as stated in this Migration Guide:
- https://www.keycloak.org/migration/migrating-to-quarkus#_migrating_custom_providers
Providers implementations are required to be plain java objects which implement the suitable User Storage SPI interfaces, as was explained in the previous sections. They must be packaged and deployed as stated in the Migration Guide.
ifeval::[{project_community}==true]
See https://www.keycloak.org/migration/migrating-to-quarkus#_migrating_custom_providers[Migrating custom providers].
endif::[]
ifeval::[{project_product}==true]
See {migration_link}migrating-providers[Migrating custom providers].
endif::[]
You can still implement your custom `UserStorageProvider` class, which is able to integrate an external database by JPA Entity Manager, as shown in this example: