You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to set some "unsupported server options" to get an access.log for Keycloak.
My problem is, that as soon as a quarkus.properties exists (even an empty one) after a kc build, Keycloak is not able to connect to the database any more as it seems to use wrong credentials.
I defined username and password for the database in conf/keycloak.conf.
What I found out so far: the problem seems to come, when kc.quarkus-properties-enabled=true is set in /META-INF/keycloak-persisted.properties inside lib/quarkus/generated-bytecode.jar.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying to set some "unsupported server options" to get an access.log for Keycloak.
My problem is, that as soon as a
quarkus.propertiesexists (even an empty one) after akc build, Keycloak is not able to connect to the database any more as it seems to use wrong credentials.I defined username and password for the database in
conf/keycloak.conf.What I found out so far: the problem seems to come, when
kc.quarkus-properties-enabled=trueis set in/META-INF/keycloak-persisted.propertiesinsidelib/quarkus/generated-bytecode.jar.What am I doing wrong here?
I'm using Keycloak 17.0.0
Beta Was this translation helpful? Give feedback.
All reactions