Skip to content
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

Open
evegufy opened this issue Nov 21, 2024 · 0 comments
Open

Enhance Keycloak seeding | Enable selective seeding #1172

evegufy opened this issue Nov 21, 2024 · 0 comments
Assignees
Labels
bug Something isn't working enhancement New feature or request

Comments

@evegufy
Copy link
Contributor

evegufy commented Nov 21, 2024

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

@evegufy evegufy added bug Something isn't working enhancement New feature or request labels Nov 21, 2024
@evegufy evegufy added this to the Release 2.3.0 (24.12) milestone Nov 21, 2024
@github-project-automation github-project-automation bot moved this to NEW USER REQUEST in Portal Nov 21, 2024
@evegufy evegufy moved this from NEW USER REQUEST to BACKLOG in Portal Nov 21, 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
@Phil91 Phil91 moved this from BACKLOG to IN PROGRESS in Portal Nov 22, 2024
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 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 26, 2024
Phil91 added a commit that referenced this issue Nov 27, 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 <[email protected]>
Reviewed-By: Evelyn Gurschler <[email protected]>
Reviewed-By: Norbert Truchsess <[email protected]>
Phil91 added a commit that referenced this issue Nov 28, 2024
Refs: #1172
Co-authored-by: Norbert Truchsess <[email protected]>
Reviewed-By: Evelyn Gurschler <[email protected]>
Reviewed-By: Norbert Truchsess <[email protected]>
@Phil91 Phil91 moved this from IN PROGRESS to IN REVIEW in Portal Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
Status: IN REVIEW
Development

No branches or pull requests

2 participants