LogoLogo
EDCDSPortalDAPS
CE 11.0.0
CE 11.0.0
  • Welcome
  • Key Concepts
  • FAQ
  • Frontend
    • Walkthrough
    • Dashboard
    • Providing
      • 1. Create Data Offer
      • 2. Create Asset
      • 3. Create Policy
      • 4. Create Contract Definition
    • Consuming
      • 1. Finding Offers
      • 2. Initiating Transfers (HttpData-Push)
      • 3. Transfer History
    • Contract Termination
  • Backend
    • Postman
    • API-Wrapper vs Management-API
    • API-Wrapper
      • Java Client Library
    • Management-API
      • Secrets API
      • Contract Definition: Multiple Assets
      • QuerySpec
      • Health Check APIs
      • Policy: Business Partner Groups
      • Policy: Unrestricted
    • Data Transfer
      • HttpData-Pull (Parameterized)
      • AWS S3 Transfer
      • Source: Audit Headers
      • Source/Sink: OAuth2/API-Key
  • Community Edition Deployment
    • Overview
    • Local Demo
    • Production
  • Customer Links
    • Glossary
    • sovity Hub
    • Service Desk
Powered by GitBook
LogoLogo

sovity

  • Homepage
  • About us
  • GitHub
  • LinkedIn

Information

  • Contact
  • Imprint
  • Privacy Policy

© by sovity GmbH

On this page
  • Additional Headers
  • Key Objectives

Was this helpful?

Edit on GitHub
  1. Backend
  2. Data Transfer

Source: Audit Headers

Requests towards data-sources include additional headers for the auditing of transfer requests by the provider’s backend service. By that, the provider can manage consumer-specific access without the need to create separate assets for each consumer.

Additional Headers

The following headers are included in the requests from the EDC's Data-Plane to the http-datasource specified in the providing asset:

  1. edc-contract-agreement-id

    • Contains the agreement-id for the specific contract between the provider and the consumer

  2. edc-bpn

    • Represents the Business Partner Number (BPN) of the consumer

Key Objectives

  • Enhanced Auditability: The backend service can log and monitor data requests made by consumers, ensuring traceability.

  • Simplified Configuration: Providers avoid the need for creating separate assets per consumer.

  • HttpData-Push Transfers: The same mechanism applies to HttpData-Push, making it straightforward.

Last updated 2 months ago

Was this helpful?