Releases · sovity/edc-ce

[v11.0.0] - 2025-03-10

Overview

Catena-X support. New custom module system with a single launcher. Migrate to Tractus-X 24.08 and Core EDC 0.7.2. Relicensing to Elastic License 2.0.

Major Changes

After careful deliberation we have decided to re-license the sovity Community Edition EDC to Elastic License 2.0
- If you are self-hosting your connectors, nothing changes for you.
- If you plan to contribute to this repository or have contributed to this repository in the past, your source code will remain under Apache License 2.0.
- If you are hosting connectors for a third party, please make sure to carefully read the Elastic License 2.0 and our explanation here
- For more details, please see our vision behind the sovity Community Edition here
Breaking changes to Connector Docker Images, Versions and Configuration:
- Unified versioning across all the sovity EDC Connectors and the sovity EDC UI for simplicity
- Unified variants through new config and module system
- Auto-documented configuration system
- All sovity-specific configuration related to the EDC is now prefixed as sovity.
Ongoing migration from Java to Kotlin
Bumped Eclipse EDC to 0.7.2
Bumped Tractus-X EDC to 0.7.7 / 24.08 Jupiter
Parameterization for HTTP Push Transfers is no longer available
- Due to our UI only supporting HTTP Push, parameterization when initiating transfers is no longer available in our UI
Referring connector policy no longer evaluates the EQ operator like IN:
- For the participant x a policy usingREFERRING_CONNECTOR EQ "x, y" does not evaluate to true anymore, because ["x"] != ["x", "y"].
- Both REFERRING_CONNECTOR IN "a, b" and REFERRING_CONNECTOR IN ["a", "b"] would work.
- Separating values by comma is still supported for the referring connector policy, it's just that it doesn't work with the EQ operator.
API Wrapper: Renamed some fields and classes for the createDataOffer endpoint
API Wrapper + Management API: Catalog requests now require a participantId
- For sovity-daps variants this is optional, because we don't use SSI, but we align ourselves with Catena-X because it is easier to maintain one way of working with the EDC than maintain two
- The UI Dashboard now gives you a Connector Endpoint + Participant ID with an appended ?participantId=... instead of just a Connector Endpoint.
  This is so the UI flow of Copy one URL from the dashboard -> Paste one URL into the Catalog remains unchanged
- The API now requires additional information of a Participant ID
API Wrapper + Management API: Transfer Initiation Requests now have an additional required "transfer type". Here's an overview over what "types" we now have:
- Transfer Type:
  - Data plane architectural flow type of the transfer
  - Decided by the consumer when initiating the transfer
  - Both data planes must support this transfer type
  - The selection might further limit what data address types are supported.
  - E.g. HttpData-PUSH,HttpData-PULL,AmazonS3-PUSH
- Data Source Type:
  - How the data plane gets the byte array of data when providing
  - Decided by the provider when creating the asset
  - The provider data plane must support this transfer type
  - E.g. HttpData, HttpProxy, HttpPush, AzureStorage, AmazonS3
- Data Sink Type:
  - How the data plane stores away the received byte array when consuming
  - Decided by the consumer when initiating a transfer
  - The consumer data plane must support this transfer type
  - E.g. HttpData, HttpProxy, HttpPush, AzureStorage, AmazonS3
Asset JSON-LD changes:
- All asset metadata under the DCAT Dataset field http://www.w3.org/ns/dcat#distribution such as mediaType
  has been moved to https://semantic.sovity.io/dcat-ext#distribution because the Eclipse EDC now overrides the field with information
  regarding available data planes, causing asset metadata to get swallowed when querying the catalog. Previously the Eclipse EDC was
  already appropriating the distribution field for its own purposes, but because they used an incorrect DCAT context
  prefix https:// instead of http://, it did not collide. Now they corrected it, so it collides, so we had to move our asset metadata
  to a custom field instead of following the DCAT standard.
Published JARs have changed:
- api - JAX-RS Interfaces for both our sovity EDC CE and sovity EDC EE
- java-client - Java API Client library for both our sovity EDC CE and sovity EDC EE
- mappers-lib - Utilities for parsing Asset JSON-LD, Policy JSON-LD and DCAT Catalog JSON-LD payloads
- jsonlld-lib - Utilities for dealing with Eclipse EDC JSON-LD
Reworked DAPS interaction:
- The Client ID in the Keycloak must now be the Participant ID
  - SKI/AKI as a concept does not exist anymore
  - DAPS variants require re-registration of the connector at the DAPS under a new Client ID
  - The certificate can be re-used, but by experience a new client needs to be registered in the Keycloak, renaming does not seem to work.
- The provider audience remains unchanged. It is expected to be the same as the Token URL
- The endpoint audience was changed from ~~idsc:IDS_CONNECTORS_ALL~~ to edc:dsp-api
- The claim ~~referringConnector~~ has been removed in favor of azp, which is a default claim and should contain the Client ID
  which should now coincide with the Participant ID

Minor Changes

All variants now support being launched as Control Plane with an integrated Data Plane
Hashicorp vault support
Build information now shows release version instead of commit information
Developer XP and debugging utilities:
- sovity.print.config - Print effective config, dependency jars and extensions. Never use on customer connectors!
- In-memory vault with initialization via env
- Improved ability to test variants and versions thanks to the new module system
- Improved ability to surgically replace EDC Extensions thanks to the new module system
- All used EDC Configuration is now documented
- All used vault entries are now documented
Added more explicit legacy Omejdn DAPS support. Note, that this is not tested

Patch Changes

Fixed a bug fetching over 5000 elements by fixing transaction use for API enpdoints.

Known Issues

Known issues to be fixed in upcoming releases.

Documentation is currently still not up-to-date.
Catena-X policies are currently not properly supported via the UI.

Deployment Migration Notes

Please re-deploy all connectors using our reworked Productive Deployment Guide
- The configuration of our connectors has been reworked for better documentation and flexibility.
- Database migration histories are not compatible. Migrating was unfortunately not possible due to missing information in the DB, that would have to be amended on both provider and consumer sides.
- Note that the sovity EDC CE UI image is now named edc-ce-ui instead of ~~edc-ui~~.
Preconfigured Catalog URLs now require a suffix of ?particpantId=... as they are no longer pure Connector Endpoints but a list of Connector Endpoint + Participant ID
Base Paths for the Connector Backends are no longer opinionated. If you continue to want to have given base paths /control / /data,
you need to configure them using the recommended properties.

Compatible Versions

EDC CE Backend: ghcr.io/sovity/edc-ce:11.0.0
EDC CE Frontend: ghcr.io/sovity/edc-ce-ui:11.0.0
PostgreSQL: 16
Eclipse EDC Fork: v0.7.2.1
Tractus-X: 0.7.7

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[v11.0.0] - 2025-03-10

Overview

Major Changes

Minor Changes

Patch Changes

Known Issues

Deployment Migration Notes

Compatible Versions

[10.5.1] - 2024-12-16

Overview

Detailed Changes

Patch Changes

Deployment Migration Notes

Compatible Versions

[10.5.0] - 2024-12-13

Overview

Detailed Changes

Minor Changes

Patch Changes

Deployment Migration Notes

Compatible Versions

[10.4.4] - 2024-12-09

Overview

Detailed Changes

Patch Changes

Deployment Migration Notes

Compatible Versions

[10.4.3] - 2024-12-04

Overview

Releases: sovity/edc-ce

v11.0.0

[v11.0.0] - 2025-03-10

Overview

Major Changes

Minor Changes

Patch Changes

Known Issues

Deployment Migration Notes

Compatible Versions

v0.0.1-20241101-2408-alpha9

10.5.1

[10.5.1] - 2024-12-16

Overview

Detailed Changes

Patch Changes

Deployment Migration Notes

Compatible Versions

10.5.0

[10.5.0] - 2024-12-13

Overview

Detailed Changes

Minor Changes

Patch Changes

Deployment Migration Notes

Compatible Versions

10.4.4

[10.4.4] - 2024-12-09

Overview

Detailed Changes

Patch Changes

Deployment Migration Notes

Compatible Versions

10.4.3

[10.4.3] - 2024-12-04

Overview

v0.0.1-20241101-2408-alpha8

v0.0.1-20241031-2408-alpha7

v0.0.1-20241031-2408-alpha6

v0.0.1-20241031-2408-alpha5