testcontainers-spring-boot VS keycloak-config-cli

For Spring Boot there's a nice wrapper: https://github.com/PlaytikaOSS/testcontainers-spring-boot. (I work for Playtika).

We will use the Playtika testcontainers-springboot library to easily spin up a Redis docker container while running the integration tests locally. This can then be used as our PubSub message broker as we test the functionality of the connection server.

Most of the time nowadays, I prefer offloading this to an identity provider, using OpenID Connect or soon Federated Credential Management (FedCM), even if that means shipping an identity provider as part of the deliverables (I generally go with Keycloak, with keycloak-config-cli to provision its configuration). I'm obviously biased though as I work in IT services, developping software mainly for intranets/extranets, and companies now increasingly have their own identity providers or at a minimum have that in their roadmap. So YMMV.

> But it is painful share the setup with other engineers.

We used keycloak-config-cli [1] it compares a config file stripped of IDs to your Keycloak installation and makes the relevant updates through the REST API.

[1] https://github.com/adorsys/keycloak-config-cli

As far as I know, the state of the art is https://github.com/adorsys/keycloak-config-cli , but I haven't played with that yet. It seems to be a big improvement over other solutions, because it can update configurations and the configurations can be "clean".

One alternative is to use the admin APIs instead of the UI. You'd SSH into the host and then use curl or https://github.com/adorsys/keycloak-config-cli to configure keycloak. I use the keycloak-config-cli for my setup. It's both how I manage disaster recovery and make changes to configuration.

I'm not saying that keycloak is always easy to work with. The thing I found hardest to figure out was how to automate disaster recovery. I want to be able to rebuild my entire auth configuration from scratch including users, default passwords, oauth clients, JWT mappings, etc. The only way I found to do this was to use https://github.com/adorsys/keycloak-config-cli. tl;dr It uses the admin API to provision items. You can export a configured realm, manually tweak some parts of it like enter passwords and add users, and then run it against a keycloak instance to restore everything.

I've found this https://github.com/adorsys/keycloak-config-cli and it looks really promising. It can update the configs without a need to restart the whole keycloak instance.

If you do end up using a setup like this then I highly recommend that you look into https://github.com/adorsys/keycloak-config-cli. tl;dr You can export your realm configuration once set up and then use it to restore your system should you lose your keycloak data. It can also be used to provision users but you have to manually add them to the realm export because they are not included in an export for some reason. All the different objects it can manage are documented here: https://www.keycloak.org/docs-api/17.0/rest-api/index.html#_realmrepresentation.