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
The keycloak container isn't persistent...
The keycloak client secret is known only after creating the client, but when the docker-compose file is running you can't change the env vars of the proxy container... once you change the environment variable you need to restart the compose file, which restarts keycloak and resets the client.
What I did is i added a persistent postgres container & set keycloak to use the postgres db.
The text was updated successfully, but these errors were encountered:
This is neither a problem connected to this proxy solution nor related to keycloak.
The problem here is your individual configuration. It's not a surprise that the secrets stay the same after having a common persistent container setup.
The keycloak container isn't persistent...
The keycloak client secret is known only after creating the client, but when the docker-compose file is running you can't change the env vars of the proxy container... once you change the environment variable you need to restart the compose file, which restarts keycloak and resets the client.
What I did is i added a persistent postgres container & set keycloak to use the postgres db.
The text was updated successfully, but these errors were encountered: