Replies: 3 comments
-
|
I have the same problem, except I haven't yet found a file called quarkus.properties :) |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
That's right. If it does not exist, then you can manually create one Am 14.07.2022 22:04 schrieb Joshua Tolley ***@***.***>:
I have the same problem, except I haven't yet found a file called quarkus.properties :)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I successfully used hints from #11464, and added in that thread some details on exactly what I did. Perhaps that will help you. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
In the wildfly distribution of keycloak, we were sharing a datasource defined in standalone.xml for both keycloak and a User federation
We were accessing the datasource in our code via its jndi-name. However as I understand, jndi is no supported in Quarkus by design.
How can we still use a data source that is defined in keycloak.conf or quarkus.properties to leverage the datasource and pooling of keycloak.x?
Beta Was this translation helpful? Give feedback.
All reactions