Repository navigation
Keycloak Zero-Touch Bootstrapping/ Automation - Testing/ Local Development #36606
Unanswered
kieronlanning
asked this question in
Q&A
Replies: 2 comments
|
I have some |
0 replies
|
To bootstrap an instance with pre-defined information you can run the Keycloak service with the |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Outline
I'm trying to automate the bootstrapping of a Keycloak container instance for the purposes of zero-touch integration testing, and local development work.
To achieve this, I'm using a combination of TestContainers.Net and .NET Aspire, but there is no limiting factor on technology for the automation.
The container instances are transient - they may survive for the duration of the test (seconds), or a local development session (days, weeks, etc).
Goal
What I'm trying to achieve is, from a fresh container start, is:
The secret key/ login credentials should be made available to the automation tool, which is outside of Keycloak.
The idea of this being zero-touch is that each test and/ or developer can have KC configured automatically for them and their current situation/ requirement.
I'm coming unstuck when trying to automate the creation of a service account and/ client that has those administrative permissions across the instance and the realm. Is there a guide and sample application that demos this kind of zero touch approach? I've most likely missed something, but I'm struggling to find/ see what.
I would like to avoid using something like Terraform if possible, and stick with calling the Administrative APIs if possible, as it enables devs to perform more self-service/ config, and test devcelopment. It's also how the end-product will interact with Keycloak.
All reactions