Skip to content
This repository has been archived by the owner on Jan 15, 2025. It is now read-only.

Persistent keycloak #16

Open
sagivoulu opened this issue May 18, 2020 · 1 comment
Open

Persistent keycloak #16

sagivoulu opened this issue May 18, 2020 · 1 comment

Comments

@sagivoulu
Copy link

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.

@elysweyr
Copy link

elysweyr commented Jul 5, 2020

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants