There needs to exist one account available to bootstrap Horreum.
Describe the solution you'd like
I propose that on startup, when there are no accounts registered, create one on the reserved namespace horreum. with admin role. The account will have a random generated password (for dev / test can be a default instead) that will be available in the startup logs It can be removed later on once another admin account is created.
Additional information
At the moment there is a pre-loaded account into the keycloak dev service. That 1) is not available in deployments without oidc and 2) does not answer the problem of bootstrap in production profile.
Feature idea.
There needs to exist one account available to bootstrap Horreum.
Describe the solution you'd like
I propose that on startup, when there are no accounts registered, create one on the reserved namespace
horreum.withadminrole. The account will have a random generated password (for dev / test can be a default instead) that will be available in the startup logs It can be removed later on once another admin account is created.Additional information
At the moment there is a pre-loaded account into the keycloak dev service. That 1) is not available in deployments without oidc and 2) does not answer the problem of bootstrap in production profile.