sovity EDC Community Edition
MY_EDC_PARTICIPANT_ID
must now coincide with a DAT claim.
This fixes the Contract Negotiation issue that affected 5.0.0
and 6.0.0
.
https://github.com/sovity/edc-ui/releases/tag/v2.2.0
COMPLETED
in Eclipse EDC 0.2
.MY_EDC_NAME_KEBAB_CASE
as deprecated in favor of MY_EDC_PARTICIPANT_ID
.MY_EDC_PARTICIPANT_ID
will now be validated via the DAPS:
MY_EDC_PARTICIPANT_ID
must coincide with the claim value referringConnector
as configured for this Connector in the DAPS.referringConnector
claim:
EDC_AGENT_IDENTITY_KEY
.EDC_AGENT_IDENTITY_KEY
could be set to the claim name of the AKI / SKI Client ID, which should always be part of
the issued DAT. This would be sub
for a sovity DAPS and client_id
for an Omejdn DAPS.MY_EDC_PARTICIPANT_ID
would have to be set to the AKI / SKI Client ID.MY_EDC_NAME_KEBAB_CASE
MY_EDC_PARTICIPANT_ID
. MY_EDC_NAME_KEBAB_CASE
ghcr.io/sovity/edc-dev:7.0.0
ghcr.io/sovity/edc-ce:7.0.0
ghcr.io/sovity/edc-ce-mds:7.0.0
ghcr.io/sovity/edc-ui:2.2.0
Connectors are now pre-configured for the sovity DAPS over Omejdn.
This fixes issues with MDS Connectors not being able to connect to the MDS 2.0.
https://github.com/sovity/edc-ui/releases/tag/v2.1.0
:extensions:wrapper:wrapper-common-mappers
for broker: AssetJsonLdUtils
, made some methods public.Omejdn DAPS users need to manually add the following Backend ENV Vars:
EDC_OAUTH_PROVIDER_AUDIENCE: idsc:IDS_CONNECTORS_ALL
EDC_OAUTH_ENDPOINT_AUDIENCE: idsc:IDS_CONNECTORS_ALL
EDC_AGENT_IDENTITY_KEY: client_id
ghcr.io/sovity/edc-dev:6.0.0
ghcr.io/sovity/edc-ce:6.0.0
ghcr.io/sovity/edc-ce-mds:6.0.0
ghcr.io/sovity/edc-ui:2.1.0
Re-release of v4.2.0 with fixed curl vulnerabilities.
ghcr.io/sovity/edc-dev:4.2.1
ghcr.io/sovity/edc-ce:4.2.1
ghcr.io/sovity/edc-ce-mds:4.2.1
ghcr.io/sovity/edc-ui:0.0.1-milestone-8-sovity14
Migration from Eclipse EDC Milestone 8 to Eclispe EDC 0.2.1.
The API Wrapper and API Client Libraries can now be used to fully control a sovity EDC Connector.
https://github.com/sovity/edc-ui/releases/tag/v2.0.0
0.2.1
:
:extensions:wrapper:wrapper-common-api
and :extensions:wrapper:wrapper-common-mappers
.:utils:json-and-jsonld-utils
:utils:catalog-parser
:utils:test-connector-remote
and :extensions:test-backend-controller
:launchers:common
and :launchers:connectors
so building different variants no longer requires separate builds.:extensions:wrapper:wrapper-api
split from :extensions:wrapper:wrapper
so integration tests in wrapper
can use the Java Client Library.:launchers:connectors:sovity-dev
that start two connectors and test the data exchange.https://[FQDN]/api/dsp
from https://[FQDN]/api/v1/ids/data
https://[FQDN]/api/management
from https://[FQDN]/api/v1/management
v1
Eclipse EDC Management API has been replaced by the Eclipse EDC JSON-LD
v2
Management API. Our Postman Collection shows some example requests.
However, a switch to our API Wrapper is recommended. Despite our Use Case API Wrapper API still being in development,
the Connector UI API Wrapper is fully functional and can be used in concatenation with our type-safe generated API Client Libraries to both provide and
consume data offers.ghcr.io/sovity/edc-dev:5.0.0
ghcr.io/sovity/edc-ce:5.0.0
ghcr.io/sovity/edc-ce-mds:5.0.0
ghcr.io/sovity/edc-ui:2.0.0
MDS 1.2 release using MS8 EDC.
ghcr.io/sovity/edc-dev:4.2.0
ghcr.io/sovity/edc-ce:4.2.0
ghcr.io/sovity/edc-ce-mds:4.2.0
ghcr.io/sovity/edc-ui:0.0.1-milestone-8-sovity13
Security improvements of container image and enhancements for the ReferringConnectorValidationExtension
.
eclipse-temurin:17-jre-alpine
ghcr.io/sovity/edc-dev:4.1.0
ghcr.io/sovity/edc-ce:4.1.0
ghcr.io/sovity/edc-ce-mds:4.1.0
ghcr.io/sovity/edc-ui:0.0.1-milestone-8-sovity12
Bugfixes regarding Parameterized Http Datasource Support and open-ended date intervals.
No changes besides docker image versions.
ghcr.io/sovity/edc-dev:4.0.1
ghcr.io/sovity/edc-ce:4.0.1
ghcr.io/sovity/edc-ce-mds:4.0.1
ghcr.io/sovity/edc-ui:0.0.1-milestone-8-sovity11
Parameterized Http Datasource Support and open-ended date intervals.
DataOfferDetailPage
and ConnectorDetailPage
with model.No changes besides docker image versions.
ghcr.io/sovity/edc-dev:4.0.0
ghcr.io/sovity/edc-ce:4.0.0
ghcr.io/sovity/edc-ce-mds:4.0.0
ghcr.io/sovity/edc-ui:0.0.1-milestone-8-sovity9
ghcr.io/sovity/edc-ui:0.0.1-milestone-8-sovity5
in production docker-compose.yaml
. This
fixes a CORS-related issue.