When first deploying keycloak, I was a little unsure about how to set up the real admin user. Surprisingly, the keycloak docs don't tell you how to do this, this is really all they say:
When first deploying keycloak, I was a little unsure about how to set up the real admin user. Surprisingly, the keycloak docs don't tell you how to do this, this is really all they say:
* https://www.keycloak.org/server/bootstrap-admin-recovery
* https://docs.redhat.com/en/documentation/red_hat_build_of_keycloak/22.0/html/server_administration_guide/creating-first-admin_server_administration_guide
So I wrote the directions here. Also added a section on recovery, because I messed up when creating my initial admin user and lost its password 🤦♂️
Also fixed some deprecated traefik labels as described in https://git.coopcloud.tech/coop-cloud/example/pulls/3
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When first deploying keycloak, I was a little unsure about how to set up the real admin user. Surprisingly, the keycloak docs don't tell you how to do this, this is really all they say:
So I wrote the directions here. Also added a section on recovery, because I messed up when creating my initial admin user and lost its password 🤦♂️
Also fixed some deprecated traefik labels as described in coop-cloud/example#3
One minor comment but otherwise, LGTM! Thanks!
@@ -38,0 +54,4 @@You can create a new admin account like this:```docker exec -it <keycloak container ID> bashabra app run <app> <service> bash?You can even potentially run this as a one-liner?
Looks fantastic @mac-chaffee, nice one! Merge away 👌