-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sig#578 - Enhancement keycloak seeding job to seed variables and secrets #438
Comments
Last comment from norbert: as a first step in PR #363 all code referring to UserEntityId (companyUsers) respectivly ClientId (ServiceAccounts) has been refactored to make use of username / clientClientId instead. As with this change the keycloak's primary key of those entities doesn't matter any more it allows to seed keycloak-data via the api independently from the database-content. The PR is approved, merged and successfully tested on DEV |
implemented for Client-Secrets:
to be set from the helmchart as environments-variables:
|
* feature(keycloak): add seeding data to configuration * adjust handling of null dictionary-values in seeder-settings update framework version * allow update of existing urls and secret in client * remove redundant keycloak notfound error-logging * remove ExcludedUserAttributes, add startup-validation * add credentials to user * allow override of identityproviders urls on update * create users by partial-import, fix client protocol-mappers * add seeding of protocolmappers and clientscopes * create clients via partialimport * allow import of multiple files per realm, fix client-scope updates * add error 500 messages, fix client protocolmapper creation * fix keycloak-calls uppercase dictionary keys * fix keycloak api-calls json-serialisation null-value handling * update framework version * Update src/keycloak/Keycloak.Seeding/appsettings.json --------- Refs: #438 Co-authored-by: Evelyn Gurschler <evelyn.gurschler@bmw.de>
Summary
Enhancement keycloak seeding job to seed variables and secrets
Please be aware of the changes done to the keycloak seeding in course of #346 (created as short term solution for 23.12.)
The text was updated successfully, but these errors were encountered: