Validate the incoming TLS connection against the incoming DAT about ids-messaging-services HOT 6 CLOSED

I think it's an ongoing discussion?!
Fraunhofer-AISEC/omejdn-server#38

from ids-messaging-services.

must dynamically specify their TLS certifacte fingerprint in a DAT request
Do we already have a claim or other option for this in the DAT request? If not, it would have to be added.

Would have to be specified here first (can't identify a matching claim): https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS#request-token-that-is-handed-in-at-daps-side

from ids-messaging-services.

Related:

• International-Data-Spaces-Association/omejdn-daps#21
• International-Data-Spaces-Association/omejdn-daps#22

from ids-messaging-services.

Waiting for a reference implementation in EDC as this is on the schedule there for current milestone planning. Will then adapt that here when the solution is available. (Issue 1152 in EDC)

from ids-messaging-services.

For reference, here is the current proposal for specifying the claims as a request parameter (private repo):
https://github.com/International-Data-Spaces-Association/IDS-G-pre/pull/84

from ids-messaging-services.

Here's the link to the EDC issue, which is part of the Milestone 4 for the end of the month:
"check hostname of incoming request"
eclipse-edc/Connector#1152

from ids-messaging-services.