Skip to main content

25.03

ยท 9 min read

[25.03] - 2025-03-19โ€‹

Implemented features can be found here

Addedโ€‹

ComponentHelm Chart (s)App-/KIT Version (s)
Logistics KITn/a1.0.0
Customs KITn/a1.0.0

Updatedโ€‹

ComponentHelm Chart (s)App-/KIT Version (s)
BPN DID Resolution Service (BDRS)bdrs: 0.5.40.5.4
Business Partner KITn/a8.0.0
Demand- and Capacity-Management KITn/a1.3.0
Digital Twin Registrydigital-twin-registry:0.7.00.7.0
Discovery Finderdiscoveryfinder: 0.5.10.6.1
Discovery Service (BPN Finder)bpndiscovery: 0.5.10.6.1
Eclipse Data Space Connector (Tractus-X EDC)tractusx-connector: 0.9.00.9.0
Golden Record Business Partner Number (BPN) Servicebpdm: 5.3.06.3.0
Identity and Access Management (IAM)centralidp: 4.1.0
sharedidp: 4.1.0
keycloak: 25.0.6
Industry Core KITn/a1.4.0
Item Relationship Service (IRS)item-relationship-service: 8.0.16.0.1
OSim KITn/a3.1.0
PCF KITn/a1.2.1
Policy Hubpolicy-hub: 1.3.01.3.0
Portalportal: 2.4.0registration: 2.2.0
frontend: 2.4.0
backend: 2.4.0
assets: 2.4.0
PURISpuris: 2.8.13.0.0
Quality KITn/a2.0.0
Self Description (SD) Factorysdfactory: 2.1.322.1.23
Semantic Hubsemantic-hub: 0.5.00.6.0
SSI Authority & Schema Registryssi-asr: 1.2.01.2.0
SSI Credential Issuerssi-credential-issuer: 1.3.01.3.0
Trace-X Traceability Applicationtraceability-foss: 1.4.114.0.1
Traceability KITn/a6.0.2

Removed / Deprecatedโ€‹

ComponentHelm Chart (s)App-/KIT Version (s)
Knowledge Agentsremoting-agent: 1.14.24
provisioning-agent: 1.14.24
conforming-agent: 1.14.24
matchmaking-agent: 1.14.24
remoting-agent: 1.14.24
provisioning-agent: 1.14.24
conforming-agent: 1.14.24
matchmaking-agent: 1.14.24
Digital Product Pass (DPP)digital-product-pass: 4.0.1v4.0.1

Known Knownsโ€‹

  • All not listed products and KITs have not been updated and are based on the release 24.12
    • These products were not part of the e2e testing phase
    • And are not tested with the current EDC version 0.9.0
  • The Eclipse Tractus-X release does not include an Identity Wallet. The development team decided on a temporary bridging solution, based on a commercial application, to test and ship the releases 24.08, 24.12 and 25.03. Without implementing this interim solution, participants will not be able to fully utilize this release in consequence.
  • For E2E Testing, the 2.2.1 of the SSI DIM Middle Layer was used - this component is FOSS but the currently used wallet (see previous item) is not.
  • BPNL Group Validation for a Policy does not allow a Collection as a rightOperand -> see Issue
  • EDR token refresh implementation is inconsistent and deviates from the documentation -> see Issue
  • Consumer-Asset with the same ID as a Provider-Asset Cannot Be Deleted After Contract Negotiation -> see Issue
  • Termination of pull transfer process from consumer side does not succeed -> see Issue
  • Fatal error while resume PULL transfer process -> see Issue

EDCโ€‹

  • Any EDC will not work with a Hashicorp Vault version 1.18.1 as this version has a bug, incompatibilities to other versions are not known.
  • Compared with the catalog from version 0.7.7, the "endpointUrl" property in a Dataset is always in namespace "dcat", a redundant property in namespace "dct" is not available anymore.

BDRSโ€‹

  • BDRS will not work with a Hashicorp Vault version 1.18.1 as this version has a bug, incompatibilities to other versions are not known.

Digital Product Passโ€‹

Knowledge Agentsโ€‹

  • Knowledge Agents is not part of this release but was tested with the EDC release candidate 0.8.0-RC4

Portalโ€‹

  • Note for Gaia-X Clearing House Tagus upgrade (Portal v2.4.0, Eclipse Tractus-X R25.03):
    • If a company was onboarded with ELBE clearing house, the legal person self description document is not accepted when creating a connector with newer versions of the clearing house. Portal operators are advised to create new legal person and connector self description documents for all previously onboarded companies.
    • As of v2.4.0, the portal backend will activate connector without updated legal person self description document to allow for a transition phase. The connector will not have a document until reissuance for both company and connector is triggered by operators.
    • An automatic reissuance system is planned for the future.
  • When registering two connectors (EDCs) under one technical user, the technical user will be duplicated and the details of the technical user will not be shown

Runtimeโ€‹

  • on Kubernetes versions: 1.29.10
  • with PostgreSQL versions: 15.4.0. or more specific 15.4.0-debian-11-r45
  • the EDC version 0.9.0-rc2 was used for testing
note

Tractus-X EDC has been tested on both Postgresql versions: 15.x and 16.x

tip

For installation details, please see the referenced Repositories / Releases.