feat(BpnDidService): Transition from API Key to Technical User Authentication for BDRS Integration (#59)

[tfjanjua]

Description

We need to update the authentication mechanism for our portal's integration with the BDRS. The current implementation uses an API Key, but it is needed to switch to a new authentication method using a technical user with client ID and secret.

Why

The endpoints the portal is hitting remain unchanged, however, the error handling got improved to support the new errors provided with the technical user authentication method.

Issue

Ref: #1078

Corresponding Configuration PR

eclipse-tractusx/portal#474

Checklist

• I have followed the contributing guidelines
• I have performed a self-review of my own code
• I have successfully tested my changes locally
• I have added tests that prove my changes work
• I have checked that new and existing tests pass locally with my changes
• I have commented my code, particularly in hard-to-understand areas

[Phil91]

Before approving I'd wait for the PRs to adjust the configuration in the portal repo and add the technical user in the portal-iam repo

[tfjanjua]

Before approving I'd wait for the PRs to adjust the configuration in the portal repo and add the technical user in the portal-iam repo

@Phil91 configuration PR has been attached

Seed data (related to Service Account of BDRS Management) still needs to be part of this PR

[evegufy]

Requesting changes so that the PR doesn't get merged until there's an according change on BDRS side eclipse-tractusx/sig-release#959 (comment)

[tfjanjua]

Requesting changes so that the PR doesn't get merged until there's an according change on BDRS side eclipse-tractusx/sig-release#959 (comment)

Just FYI: @evegufy | @Phil91, I have added Seed Data for a technical user for BDRS Management

[ntruchsess]

@tfjanjua as there was a conflict with latest seeding-data related changes on main I did rebase the branch on main and did a force-push to your repo. Please pull those changes before applying further commits.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[evegufy]

don't merge until change from BDRS side is clarified.
I was then also under the impression that you prediscussed the change with the BDRS committers, as commented here, but that doesn't seem the case, see eclipse-tractusx/bpn-did-resolution-service#120.