R25.03 Technical Maintenance

[MaximilianHauer]

Description

As part of the normal product maintenance, a couple of improvements/technical support items/needed upgrades are identified which are planned to take place.

Besides the linked issues, there are also continuous efforts ongoing to keep the products compliant with Eclipse Foundation Development Process as well as the TX Release Guidelines (e.g. security, IP checks, etc).

Overall (Portal, IAM, Policy-Hub, SSI)

• sig#855 - Move ProcessWorker into own Package portal#240
• sig#855 - Use process worker nuget package ssi-credential-issuer#60
• sig#855 - Use process worker nuget package SAP/ssi-dim-middle-layer#3
• sig#855 - Upgrade app dependencies portal-backend#1148
• sig#855 - Upgrade app dependencies portal-shared-components#399
• sig#855 - Upgrade app dependencies portal-frontend#1400
• sig#855 - Upgrade app dependencies portal-frontend-registration#326
• sig#855 - Upgrade app dependencies portal-assets#447
• sig#855 - Upgrade app dependencies ssi-authority-schema-registry#108
• sig#855 - Upgrade app dependencies ssi-credential-issuer#312
• sig#855 - Upgrade app dependencies policy-hub#241
• sig#855 - Upgrade to .NET 9 portal-backend#1155
• Upgrade app dependencies

Portal Backend

• Split business logic into processes portal-backend#1006
• add nullable typing for Keycloak.Library  portal-backend#1066

Portal Frontend

• sig#779 - Coding Style: file and folder naming not consistent portal-frontend#700

Portal Backend and IAM

• 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

IAM

• Decide on possible sandbox changes for upgrading to version > 25, see sig#779 - Upgrade to Keycloak version 25 portal-iam#85 (comment)

Impact

Additional information

• I'm willing to contribute to this feature

[stephanbcbauer]

@MaximilianHauer not sure if the new feature template would be helpful for this kind of tasks, but at least every feature would be described in the same manner?

[MaximilianHauer]

yes :) every issue should have a description / acceptance criteria / Test cases.

ill adjust this here tomorrow to be a bit more fitting

[stephanbcbauer]

Some hints from Release Management (@ther3sa) and Tractus-X Project Lead (@stephanbcbauer)

• Status currently in Inbox. ⇾ Only features with status backlog are considered in open planning
• Please add missing sections from the feature template, or fill them out
• Please add contributor and committer
• Please add assignee (overall responsible person who drives the feature)

[evegufy]

I move eclipse-tractusx/portal-backend#1052 into #779, as it's already done

[evegufy]

Committers:
@oyo
@ntruchsess
@Phil91
@evegufy