Participant Details Lookup Service and ParticipantInformationDetails EDC Extension

[AbdullahMuk]

Feature

Description (Problem to be solved and requirements to satisfy)

We face 4 problems in general:

• 1. Contracts / Transfer History on provider side does not contain any consumer details aside of URL and ID
• 2. Logging House only knows ID
• 3. On provider side with ProviderConfirmationPolicy no information about the consumer are available
• 4. On consumer side no validatable information are available. Workaround to set details by provider in asset details exists. But these details are not validated.

The goal is that a user of an EDC can use the participant ID to lookup to receive validated organization details from Authority Portal API.

Benefits

• Verifiable and trustable information about participants
• Complies with participant information service of IDSA architecture
• No adjustment in DSP necessary

Stakeholders

• MDS
• Mobilithek: Feature is required to comply with requirements and enhances compatibility with Mobilithek
• @jkbquabeck
• @SebastianOpriel

References

• [ProviderConfirmationPolicy] Allow data provider to explicitly confirm data requests on DSP:ContractOfferRequests as edc-ce#605

Solution Design

Affected Areas and Components

• authority-portal API
• edc-ce (later for the Lookup Extension)

General Requirements

• The implementation shall take into consideration that in the future the lookup service might be externalized with a write-through cache to satisfy high-load scenarios.

Out of scope

• request

Processes

Developer UX via API

• As an developer I call an API either with one ID or a set of IDs and receive necessary organization details: participant ID, Legal Name, Commerce Register Number, Website, Main Address, Main Contact (name+email)

Iterations

• PoC Implement Participant Details Lookup Service endpoint to receive validated information about specific ID; Protect via (to be refined) secret parameter/path mapping; This enables manual lookup of participant information. Authority Portal Catalog UI adjustment adding a hint about necessary confirmation;
• MvP Implement ParticipantInformationDetails EDC Extension. Integrate extension into EDC.
• Later Integrate extension into Logging House.

Work Breakdown

EDC-CE / API Wrapper

Beta Give feedback

1. Add another API Wrapper endpoint for Contract Details which adds all organization details of the counter-party consumer/provider.

Authority Portal

Beta Give feedback

1. Implement API endpoint
2. Secure API endpoint with parameter/path mapping (TBD)

Architecture

[SebastianOpriel]

Refactored: Will be covered completely by issue sovity/edc-ce#605