-
Notifications
You must be signed in to change notification settings - Fork 22
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
Enhance Keycloak seeding | Enable selective seeding #1172
Labels
Milestone
Comments
Phil91
added a commit
that referenced
this issue
Nov 22, 2024
8 tasks
Phil91
added a commit
that referenced
this issue
Nov 22, 2024
Phil91
added a commit
that referenced
this issue
Nov 22, 2024
Phil91
added a commit
that referenced
this issue
Nov 22, 2024
Phil91
added a commit
that referenced
this issue
Nov 22, 2024
Phil91
added a commit
that referenced
this issue
Nov 22, 2024
Phil91
added a commit
to eclipse-tractusx/portal-iam
that referenced
this issue
Nov 22, 2024
Phil91
added a commit
to eclipse-tractusx/portal-iam
that referenced
this issue
Nov 22, 2024
6 tasks
Phil91
added a commit
that referenced
this issue
Nov 22, 2024
Phil91
added a commit
that referenced
this issue
Nov 25, 2024
Phil91
added a commit
to eclipse-tractusx/portal-iam
that referenced
this issue
Nov 25, 2024
Phil91
added a commit
that referenced
this issue
Nov 25, 2024
Phil91
added a commit
that referenced
this issue
Nov 25, 2024
Phil91
added a commit
that referenced
this issue
Nov 25, 2024
Phil91
added a commit
that referenced
this issue
Nov 26, 2024
Phil91
added a commit
that referenced
this issue
Nov 26, 2024
Phil91
added a commit
that referenced
this issue
Nov 26, 2024
Phil91
added a commit
that referenced
this issue
Nov 27, 2024
Phil91
added a commit
to eclipse-tractusx/portal-iam
that referenced
this issue
Nov 28, 2024
Refs: eclipse-tractusx/portal-backend#1172 --------- Co-authored-by: Evelyn Gurschler <evelyn.gurschler@bmw.de> Reviewed-By: Evelyn Gurschler <evelyn.gurschler@bmw.de> Reviewed-By: Norbert Truchsess <norbert.truchsess@t-online.de>
Phil91
added a commit
that referenced
this issue
Nov 28, 2024
Refs: #1172 Co-authored-by: Norbert Truchsess <norbert.truchsess@t-online.de> Reviewed-By: Evelyn Gurschler <evelyn.gurschler@bmw.de> Reviewed-By: Norbert Truchsess <norbert.truchsess@t-online.de>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current Behavior
During testing the upgrade of the realm config of the sharedidp Keycloak instance, I noticed that in the master realm the admin realm roles for all clients that were created during runtime were removed when running the seeding job.
This - create, update and delete roles - is desired for the CX-Central (centralidp) and the CX-Operator (sharedidp) and is currently the default behavior.
But I didn't consider how this would affect the master realm, in which we don't want to to any other change than creating and updating two service accounts.
Desired Behavior
Maintain the default behavior but enable to selectively seed only certain entities (clients, roles, etc.) per realm when needed.
Please also provide the information, which methods (create, update, delete) the seeding job currently executes for each enabled entity.
Steps To Reproduce
Detected in 4.0.0-iam-rc.2/2.3.0-RC3
The text was updated successfully, but these errors were encountered: