IAM Seeding Data and IDP Seeding Jobs Enhancement

[jjeroch]

Description

Currently, the IAM seeding data are located in the portal backend repository. This feature ticket aims to move the IAM seeding data into the IAM repository where the identity provider (IDP) application and database are located. Additionally, the IDP seeding jobs are to be enhanced to include secrets and variables. These tasks will support the application maintenance and clearer application separation.

Tasks

• Move IAM seeding job from portal backend repo to IAM repo
  • Move IAM seeding | Publish Keycloak library to nuget portal-backend#611
  • Move IAM seeding | Enable job in portal-iam repository portal-iam#88
  • Move IAM seeding | Enable Workflows portal-iam#87
• Enhance IDP seeding jobs to include secrets and variables
  • sig#578 - Enhancement keycloak seeding job to seed variables and secrets portal-backend#438
  • sig#578 - Enable IAM helm charts to seed variables and client secrets  portal-iam#86

Benefits

• Clearer application separation
• Easier application maintenance
• Improved security with the inclusion of secrets and variables in IDP seeding jobs

[stephanbcbauer]

Was presented in the open planning ⇾ done internally within in the portal team, developer and committer are involved

[stephanbcbauer]

Hello @jjeroch , @evegufy

Since the feature is a 24.08 feature and the development phase is coming to an end, we need a status on the feature.

• Currently you are assigned (Responsible) → Is this correct? If not, please assign the correct contact person
• Please check whether the status (backlog, work in progress ...) is set correctly
• Please check whether there is an assignment to a committee or expert group (supported-by) to be found on the board
• Please comment on the current status of the feature
• Are all SubTasks (issues from other repositories that deal with the feature) linked? → The easiest way is to mention the feature here in the issue (via the ID) so we can see which teams/repositories are involved.

If you need any clarification, please get in touch, thank you very much.
Stephan

[jjeroch]

Update
Moved to 24.12.
Likely the ticket still might have some items which might delay further to 24.12.

Status
Implementation started; but without releasing any functions so far.

[evegufy]

Committers:
@evegufy
@Phil91
@ntruchsess
@oyo