NFR - Communication must be reliable and secured

[DanielaWuensch]

Feature Request

Non-functional Requirement - Communication must be reliable and secured
Communication must be reliable and secured (e.g. by using mTLS, by using recommended cryptography only)
Identified gaps:

• EDC mgt APIs just authentificate based on secret (API key).
• EDC Control <-> EDC Control: Client requests DAT Token from DAPS server
• EDC Data <-> EDC Data: Provider generates JWT Token with self signed Keypair and Provider Data Plane validates this token

Which Areas Would Be Affected?

all, including DPF, CI, build, transfer, etc._

Why Is the Feature Desired?

Security Requirement

Solution Proposal

Communication must be reliable and secured (e.g. by using mTLS, by using recommended cryptography only)

Type of Issue

non-functional requirement

Checklist

all communications must be reliable and secured (e.g. by using mTLS, by using recommended cryptography only)
Check in place