(Dev/INT) Prepare to run BPN:DID Resolver Component

[jjeroch]

Scope

Participant gets enabled to resolve a participant BPN to a did
Possible Reference solution: https://github.com/Metaform/bdrs/tree/main
https://github.com/eclipse-tractusx/bpn-did-resolution-service

###Architecture

Authentication

Thinking about enabling access via SSI VCs (e.g. all companies with a membership credential can access the service)
The VC is ideally put into the header

Request Details

GET via BPN the did (via the did-regsitry)

{
"content": {
   ["{BPNL}","{did}"],
   ["{BPNL}","{did}"],
   ["{BPNL}","{did}"]
 }
}

• only response those where did is existing
• if we have duplicates; we provide

Non-Tech

• Highly available
• All connectors (no matter where they are located) would need to call the service (...note: we are thinking about a connector cache strategy)

Details

After running the refinement; we aligned that the reference solution https://github.com/eclipse-tractusx/bpn-did-resolution-service will be taken over by us.
We will run the service inside our internal env.; the team around the reference solution development will support on functional development as well as bug fixing.

Ticket stays in place for Helm Chart review; environment config file creation; etc....

[jjeroch]

Open discussion: authentication with SSI or OIDC

[jjeroch]

Decision: component development in place https://github.com/eclipse-tractusx/bpn-did-resolution-service

[evegufy]

consortia specific config is kept in the following branch: https://github.com/eclipse-tractusx/bpn-did-resolution-service/tree/chore/consortia-env

[evegufy]

BDRS runs now stable on int (and dev) with the 0.0.4 version
https://github.com/eclipse-tractusx/bpn-did-resolution-service/tree/chore/0.0.4_on_consortia-envs
History: eclipse-tractusx/bpn-did-resolution-service@f92ceec

[jjeroch]

setting ticket to "user ready" tests are successfully started