Releases: sovity/edc-ce
v13.0.3
[v13.0.3] - 2025-05-21
Overview
Bumped Eclipse EDC to 0.11.1
and Tractus-X EDC to 0.9.0
. sovity API Wrapper improvements for Use Case App support. Chat App Use Case App Demo added as a permanent interactive tutorial and example.
Major Changes
- Major migrations
- Java
17
→21
- Eclipse EDC
0.7.2
→0.11.1
- Tractus-X EDC
0.7.7
→0.9.0
- The sovity EDC Java API Client Library is still available as Java 17.
- Postgres
16
→17
- Java
Minor Changes
- "Chat App" - Example Use Case App and interactive tutorial to be refined over time demonstrating the current sovity-endorsed way of building Use Case Apps with each version of the sovity EDC
- Use Case API and UI API improvements
- Well-Typed data sinks / transfer initiations
- Well-Typed catalog filtering
- Well-Typed batch negotiation by catalog filter
- HTTP Proxy & EDR Support in API Wrapper
- Batch endpoint for fetching Contract Negotiation States
- Batch endpoint for fetching Transfer Process States
- Callback support: Get notified on Negotiation Success / Failure
- Callback support: Get notified on Transfer Success / Failure / Started
- Easier handling of EDC configuration properties in Bash environments,
SOVITY_EDC_CONFIG_JSON
can be set to additional config, e.g.{"my.difficult.prop-for-bash": "value"}
. This helps with config properties containing dots and dashes.
Patch Changes
- Fixed the 404 when opening the create asset page CE#1127
- Fixed a query caching issue between assets and data offers for the publish data offer page
- Fixed EDRs not working correctly due to path configuration bugs
- Fixed issues with OAuth-protected data sources/sinks
- Optimized the dashboard API endpoint for better performance
- Optimized catalog detail page with new
getCatalogDataOffer
endpoint - Removed obsolete mobility dataspace elements from the asset model, while keeping some fields for now
Deployment Migration Notes
- Property changes for Catena variant control- and data planes:
- renamed
edc.iam.sts.dim.url
→tx.edc.iam.sts.dim.url
- renamed
- Property changes for standalone data planes:
- removed
sovity.internal.cp.management.api.url
- removed
sovity.internal.cp.management.api.key
- removed
sovity.internal.cp.management.api.key.header
- removed
- The transfer type (https://w3id.org/edc/v0.0.1/ns/transferType) in when doing a custom transfer request is now mandatory.
Compatible Versions
- EDC CE Backend:
ghcr.io/sovity/edc-ce:13.0.3
- EDC CE Frontend:
ghcr.io/sovity/edc-ce-ui:13.0.3
- PostgreSQL:
17
- Eclipse EDC Fork: v0.11.1.1
- Tractus-X:
0.9.0
v0.0.1-20250520-2408-alpha12
Internal Release Only
Pre-release / internal work-in-progress version of the Eclipse EDC 0.7 migration for internal validation
Remove the "ALL" log line.
Changes: https://github.com/sovity/edc-ee/compare/v0.0.1-20250520-2408-alpha11..v0.0.1-20250520-2408-alpha12
v0.0.1-20250520-2408-alpha11
Internal Release Only
Pre-release / internal work-in-progress version of the Eclipse EDC 0.7 migration for internal validation
Patch for t participant ID when fetching a 0.8.0+ catalog (moved to https://w3id.org/dspace/v0.8/participantId)
Changes: https://github.com/sovity/edc-ee/compare/v0.0.1-20241101-2408-alpha9..v0.0.1-20250520-2408-alpha11
v12.0.0
[v12.0.0] - 2025-04-08
Overview
EDC UI Rework in React + Next + ShadCN-UI + Tailwind with a new look-and-feel and more flexibility for future implementations.
Major Changes
- The EDC UI has been rewritten in React + NextJS + ShadCN-UI + Tailwind with a new look-and-feel
- Linkable detail / action pages for catalogs, catalog data offers, contracts and assets
- The catalog fetching multiple connector catalogs at once has been retired in favor of linkable pages and quick access to preconfigured counterparty catalog
- New style: Prefer Custom Tailwind Style to Angular Material Style
- New style: Prefer tables to cards
- New style: Prefer single-page forms with sections to wizards
- New style: Prefer linkable pages to dialogs and slide-overs
- The EDC UI config system has been reworked. The system of
EDC_UI_
-prefixed environment variables has been replaced by theUiConfig
API object. See deployment migration notes for detailed changes to the configuration of affected components
Patch Issues
- Improved Catalog performance 4-fold by optimizing parts of the Eclipse EDC Java code in our fork. Unfortunately, due to the catalog request being
O(N²)
due to in-code filtering of contract definitions and application of policies, this only allows for twice the amount of contract definitions before hitting constraints. Core-EDC Fork 0.7.2.2
Known Issues
- EDRs have issues on this version
- Documentation is out-of-date and will be amended on subsequent releases
- Some detail page requests are unoptimized right now:
- Missing findById implementations
- Frontend-side pagination
Deployment Migration Notes
- Connector Backend config changes:
- Removed all config
/edc.ui.*
EDC_UI_*
- Added
sovity.edc.ui.preconfigured.counterparties
: Pre-configured counterparties for the EDC UI catalog, format must behttps://connector/api/dsp?participantId=...
- Added
sovity.edc.ui.logout.url
: Logout URL used in EDC UI (optional) - Added
sovity.edc.ui.documentation.url
: Documentation URL used in EDC UI (optional) - Added
sovity.edc.ui.support.url
: Support URL used in EDC UI (optional) - Added
sovity.edc.ui.legal.notice.url
: Legal Notice URL used in EDC UI (optional) - Added
sovity.edc.ui.privacy.policy.url
: Privacy Policy URL used in EDC UI (optional)
- Removed all config
- EDC UI config changes:
- Removed all config
/edc.ui.*
EDC_UI_*
- Added config
NEXT_PUBLIC_MANAGEMENT_API_URL
andNEXT_PUBLIC_MANAGEMENT_API_KEY
(optional) - Added config
NEXT_PUBLIC_BUILD_DATE
andNEXT_PUBLIC_BUILD_VERSION
(override only, set by default)
- Removed all config
Compatible Versions
- EDC CE Backend:
ghcr.io/sovity/edc-ce:12.0.0
- EDC CE Frontend:
ghcr.io/sovity/edc-ce-ui:12.0.0
- PostgreSQL:
16
- Eclipse EDC Fork: v0.7.2.2
- Tractus-X:
0.7.7
v11.0.0
[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 likeIN
:- For the participant
x
a policy usingREFERRING_CONNECTOR EQ "x, y"
does not evaluate totrue
anymore, because["x"] != ["x", "y"]
. - Both
REFERRING_CONNECTOR IN "a, b"
andREFERRING_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.
- For the participant
- 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 aConnector Endpoint
.
This is so the UI flow ofCopy one URL from the dashboard -> Paste one URL into the Catalog
remains unchanged - The API now requires additional information of a Participant ID
- For
- 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
- Transfer Type:
- Asset JSON-LD changes:
- All asset metadata under the DCAT Dataset field
http://www.w3.org/ns/dcat#distribution
such asmediaType
has been moved tohttps://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 thedistribution
field for its own purposes, but because they used an incorrect DCAT context
prefixhttps://
instead ofhttp://
, 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.
- All asset metadata under the DCAT Dataset field
- Published JARs have changed:
api
- JAX-RS Interfaces for both our sovity EDC CE and sovity EDC EEjava-client
- Java API Client library for both our sovity EDC CE and sovity EDC EEmappers-lib
- Utilities for parsing Asset JSON-LD, Policy JSON-LD and DCAT Catalog JSON-LD payloadsjsonlld-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
toidsc:IDS_CONNECTORS_ALL
edc:dsp-api
- The claim
has been removed in favor ofreferringConnector
azp
, which is a default claim and should contain the Client ID
which should now coincide with the Participant ID
- The Client ID in the Keycloak must now be 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 pureConnector Endpoints
but a list ofConnector 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
v0.0.1-20241101-2408-alpha9
Internal Release Only
Pre-release / internal work-in-progress version of the Eclipse EDC 0.7 migration for internal validation
Patch for the 5k limit
Changes: https://github.com/sovity/edc-ee/compare/v0.0.1-20241031-2408-alpha8..v0.0.1-20241101-2408-alpha9
10.5.1
[10.5.1] - 2024-12-16
Overview
Update for publishing missing dependencies.
Content and function wise, this version is identical to version 10.5.0.
Detailed Changes
Patch Changes
- EDC:
- Added missing publish statements in certain dependencies
Deployment Migration Notes
No special deployment migration steps required
Compatible Versions
- Connector Backend Docker Images:
- Dev EDC:
ghcr.io/sovity/edc-dev:10.5.1
- sovity EDC CE:
ghcr.io/sovity/edc-ce:10.5.1
- MDS EDC CE:
ghcr.io/sovity/edc-ce-mds:10.5.1
- Dev EDC:
- Connector UI Docker Image:
ghcr.io/sovity/edc-ui:4.1.8
10.5.0
[10.5.0] - 2024-12-13
Overview
MDS Patch Update
Detailed Changes
Minor Changes
- Catalog now only returns
Datasets
with validOffers
(#1065)
Patch Changes
- EDC UI:
Deployment Migration Notes
No special deployment migration steps required
Compatible Versions
- Connector Backend Docker Images:
- Dev EDC:
ghcr.io/sovity/edc-dev:10.5.0
- sovity EDC CE:
ghcr.io/sovity/edc-ce:10.5.0
- MDS EDC CE:
ghcr.io/sovity/edc-ce-mds:10.5.0
- Dev EDC:
- Connector UI Docker Image:
ghcr.io/sovity/edc-ui:4.1.8
10.4.4
[10.4.4] - 2024-12-09
Overview
MDS patch update
Detailed Changes
Patch Changes
- Synchronized Crawler DB migrations with AP
Deployment Migration Notes
No special deployment migration steps required
Compatible Versions
- Connector Backend Docker Images:
- Dev EDC:
ghcr.io/sovity/edc-dev:10.4.4
- sovity EDC CE:
ghcr.io/sovity/edc-ce:10.4.4
- MDS EDC CE:
ghcr.io/sovity/edc-ce-mds:10.4.4
- Dev EDC:
- Connector UI Docker Image:
ghcr.io/sovity/edc-ui:4.1.6
10.4.3
[10.4.3] - 2024-12-04
Overview
This release has been retracted.
- Connectors and external libraries are not affected and can continue to use this version.
- Catalog Crawlers need to use version
10.4.2