-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow using an additional persistence unit and datasource #10579
Milestone
Comments
Some initial changes to make the quickstart work are here https://github.com/pedroigor/keycloak-quickstarts/tree/issue-10579. I'm going to be looking now how to make the changes less painful for those migrating from Wildfly. |
pedroigor
added a commit
to pedroigor/keycloak
that referenced
this issue
Mar 7, 2022
abstractj
pushed a commit
that referenced
this issue
Mar 8, 2022
Liu-Junlin
pushed a commit
to Liu-Junlin/keycloak
that referenced
this issue
Mar 10, 2022
pedroigor
added a commit
to pedroigor/keycloak
that referenced
this issue
Mar 21, 2022
stianst
pushed a commit
that referenced
this issue
Mar 21, 2022
Thanks for your answers. I will see this :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Discussed in #10547
Originally posted by dasniko March 2, 2022
In the server development docs at https://www.keycloak.org/docs/latest/server_development/index.html#leveraging-jakarta-ee it is mentioned how Jakarta EE resources can be used in a User Storage Provider. There‘s also the quickstart-example https://github.com/keycloak/keycloak-quickstarts/tree/latest/user-storage-jpa
With the Quarkus-based distribution of Keycloak, usage of Jakarta EE APIs like session/stateless beans is no longer possible, like also mentioned here: https://www.keycloak.org/migration/migrating-to-quarkus (end of the document).
With Quarkus it is possible to configure multiple database connections.
Will this also be the case for Keycloak itself with Keycloak config params?
And how can/will these database connections be used in a User Storage Provider? Or will this no more be possible in current Keycloak versions? What about the documentation and quickstart-examples?
If this won‘t be possible anymore, it would mean to break many custom User Storage Provider implementations. Users/customers are already starting to complain in other forums:
Can you please give us an update to this?
The text was updated successfully, but these errors were encountered: