The overarching project is guided by https://catena-x.net and all development work is covered in https://eclipse-tractusx.github.io.
All notable changes on the overarching level are documented in this file. Refer to component repositories for specific content, changelog and documentation.
The format is based on Keep a Changelog.
Tractus-X operates on YY.0M.MICRO Calendar Versioning for overarching, quarterly Releases. Semantic Versioning remains unchanged for all components.
| Category | Meaning |
|---|---|
| Added | This component was not part of a previous release package |
| Updated | The component was already part of some previous release, but has now undergone a change |
| Removed / Deprecated | The component was deliberately removed from the scope of the release package |
The success of Tractus-X and each of our releases is driven by the strength and dedication of our community. We would like to thank everyone who contributed to making the 25.03 release possible.
Whether by reporting issues, engaging in constructive discussions, proposing solutions, writing code, reviewing pull requests, improving documentation, or supporting others in the community, every contribution plays an important role in moving the project forward.
Open collaboration is at the heart of Tractus-X, and this release once again demonstrates what can be achieved. Your expertise, commitment, and willingness to collaborate are what make continuous innovation possible.
:::info
Thank You for your ongoing support and contributions.
We are looking forward to continuing this journey together with the community and to building the next releases of Tractus-X.
:::
:::info
The above list contains all contributors and committers that have been involved in this release. The list is generated automatically based on the amount of contributions to the repositories of the Eclipse Tractus-X organization on GitHub.
It's not only about code contributions, but also about reporting issues, discussing solutions, writing documentation, or reviewing contributions.
:::
Our KITs are continuously evolving, with new additions and updates happening. The planned KITs can be found in the sig-release issue list (filtered by milestone 26.03).
| KIT Name | KIT Version | Release Check |
|---|---|---|
| AI Service KIT | 0.0.1 | #1574 |
| CBAM KIT | 0.1.0 | #1625 |
| Company Certificate Management KIT | 0.1.0 | n/a |
| Due Diligence Check KIT | 0.0.1 | #1624 |
| Engineering as a Service (EaaS) KIT | 0.0.1 | #1552 |
| Modular Engineering (ModEng) KIT | 0.0.1 | #1562 |
| KIT Name | KIT Version | Release Check |
|---|---|---|
| Connector KIT | 4.0.0 | #1582 |
| Digital Twin KIT | 2.0.2 | #1560 |
| EcoPass KIT | 1.5.1 | #1579 |
| PURIS KIT | 0.4.1 | #1591 |
| Traceability KIT | 8.0.0 | n/a |
- All not listed KITs have not been updated and are based on the release 25.12 or previous releases
The planned and implemented features can be found in the sig-release issue list (filtered by milestone 26.03). These features describe only the requested new function/functionality.
Most of the features are linked to product specific issues. Please have a look on product specific repositories for detailed information on the product specific issues tabs.
| Component Name | Helm Chart (s) | App Version (s) | Release Check |
|---|---|---|---|
| Identity Hub | Holder Wallet: v0.2.0 Issuer Service: v0.2.0 |
Holder Wallet App: v0.2.0 Issuer Service App: v0.2.0 |
#1584 |
:::note
- The product
Release Checksissues for each product have been updated to reflect the new versions of the components included in this release. Please refer to these issues for detailed information on the updates.
:::
| Component Name | Helm Chart (s) | App-/KIT-/ Model- Version (s) | Release Check |
|---|---|---|---|
| Digital Twin Registry | digital-twin-registry:0.11.0 | 0.11.0 | #1594 |
| Golden Record Business Partner Number (BPN) Service | bpdm: 6.3.0 | 7.3.0 | #1592 |
| Industry Core Hub | industry-core-hub:0.5.0 | v0.5.0 | #1583 |
| Tractus-X Software Development KIT (SDK) | n/a | v0.7.1 | #1585 |
| Tractus-X Connector (Eclipse Dataspace Components Connector) | tractusx-connector: 0.12.0 | 0.12.0 | #1580 |
- All not listed products and KITs have not been updated and are based on the release 25.12 or previous releases
- These products were not part of the testing phase
- 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, 25.03, 25.06, 25.09 and 25.12. Without implementing this interim solution, participants will not be able to fully utilize this release in consequence.
- For E2E Testing, the 2.2.3 of the SSI DIM Middle Layer was used - this component is FOSS but the currently used wallet (see previous item) is not
- Due to last minute vulnerabilties, E2E tests were not executed on the latest code state (#1620 was not covered by E2E tests)
- Due to vulnerabilties present in the base layer, the BPDM images offered in Dockerhub currently contain vulnerabilities
- The identity hub wallet was not tested with a Tractus-X EDC Connector yet (planned for R26.06) to be fully functional
- The issuer service is not integrated with the portal backend (because of a limitation from the portal for the bring your own wallet topic)
- The wallet currently supports only one issuer (is configuration issue)
- Currently there is not possible to issue the membership credential as defined in the CX-0050 standard from Catena-X, because of a missing feature in upstream: Possible BUG: JWT credential @context is hardcoded and not configurable via CredentialDefinition API
- Custom Contexts are not allowed, so the "memberOf" key is not possible to be included.
- The notification api is not working for saturn because of a Bug: Backend notifications API is not compatible with Saturn connector. industry-core-hub#529 (which can not be fixed until the end of the release, however is a additional feature)
- Notifications can't be sent via frontend. Currently this is not implemented.
- Digital Product Passport consumption can fail if policy configuration was not made correctly in the connector.
The following runtime has been used during end-to-end test:
- Kubernetes version:
1.33.1 - Applications used
- PostgreSQL version:
15.4.0or higher - DTR version 0.10.0
- PostgreSQL version:
:::note
Tractus-X Connector has been tested on both Postgresql versions: 15.x and 16.x
:::
You can search all released helm charts with the following commands:
helm repo add tractusx-dev https://eclipse-tractusx.github.io/charts/dev
helm repo update tractusx-dev
helm search repo tractusx-dev --versionsThe official Bitnami Helm chart repository has been deprecated or is no longer maintained in its previous location. Bitnami has migrated legacy
container images to a new repository called bitnamilegacy. Helm charts using Bitnami container images must be updated to reference this new source
to ensure continued functionality. With bitnamilegacy we won’t receive security updates.
:::tip
If you are using a provided helm chart from Eclipse Tractus-X that uses Bitnami container images and it doesn't work, please check the values.yaml file of the respective chart
and update/overwrite the image repository from bitnami/<image-name> to bitnamilegacy/<image-name>.
:::
Extract from values.yaml:
postgresql:
image:
# -- workaround to use bitnamilegacy chart
repository: bitnamilegacy/postgresql
tag: 15.4.0-debian-11-r45:::tip
For installation details, please see the referenced Repositories / Releases and related documentation (e.g. migration documentation)
:::
| Semantic Model Name | Model Version |
|---|---|
| io.catenax.batch | 4.0.0 |
| io.catenax.material_accounting | 1.0.0 |
| io.catenax.pcf_for_battery_component_supplier | 1.0.0 |
| io.catenax.sbom | 1.0.0 |
| io.catenax.shared.standard_codes | 1.0.0 |
| io.catenax.shared.material_classification | 1.0.0 |
| io.catenax.shared.industry_core.common | 1.0.0 |
| io.catenax.shared.industry_core.manufacturing_information | 1.0.0 |
| io.catenax.shared.industry_core.site_information | 1.0.0 |
| Semantic Model Name | Model Version |
|---|---|
| io.catenax.just_in_sequence_part | 4.0.0 |
| io.catenax.part_type_information | 2.0.0 |
| io.catenax.serial_part | 4.0.0 |
| io.catenax.single_level_bom_as_built | 4.0.0 |
| io.catenax.single_level_bom_as_planned | 4.0.0 |
| io.catenax.single_level_usage_as_built | 4.0.0 |
| io.catenax.generic.digital_product_passport | 7.0.0 |
| io.catenax.us_tariff_information | 2.0.0 |
| io.catenax.single_level_usage_as_planned | 3.0.0 |
| io.catenax.quantity | 3.0.0 |
| Semantic Model Name | Model Version |
|---|---|
| io.catenax.single_level_usage_as_planned | 1.0.0 |
| io.catenax.shared.part_classification | 1.0.0 |
| io.catenax.shared.part_site_information | 1.0.0 |
| io.catenax.shared.part_site_information | 2.0.0 |
| io.catenax.shared.quantity | 1.0.0 |
- All not listed semantic models have not been updated and are based on the release 25.12 or previous releases
Our community and results/releases depends on our contributors. We want to thank everyone who has contributed to this release by reporting issues, discussing solutions, writing code, or reviewing contributions.
:::note
The above list contains all contributors and committers that have been involved in this release. The list is generated automatically based on the amount of contributions to the repositories of the Eclipse Tractus-X organization on GitHub.
It's not only about code contributions, but also about reporting issues, discussing solutions, writing documentation, or reviewing contributions.
:::
:::note
The planned and implemented features can be found in the sig-release issue list (filtered by milestone 25.12). These features describe only the requested new function/functionality.
Most of the features are linked to product specific issues. Please have a look on product specific repositories for detailed information on the product specific issues tabs.
:::
:::info
We are excited to announce the launch of KIT 2.0 Architecture - a major redesign of how we visualize and organize our KIT ecosystem. This update brings a fresh perspective to understanding the layered architecture of Eclipse Tractus-X, making it easier than ever to explore and navigate our comprehensive collection of KITs.
For further information, please refer to the following link. If you are interested in what has changed on our website, please visit this changelog.
:::
| Component | Helm Chart (s) | App-/KIT Version (s) | Release Check |
|---|---|---|---|
| Geometry KIT | n/a | 1.0.0 | n/a |
:::note
- The product
Release Checksissues for each product have been updated to reflect the new versions of the components included in this release. Please refer to these issues for detailed information on the updates. - The KITs
Release Checksissues were also updated.
:::
| Component | Helm Chart (s) | App-/KIT Version (s) | Release Check |
|---|---|---|---|
| Business Partner KIT | n/a | 11.0.0 | #1551 |
| Data Driven Quality Management KIT | n/a | 2.1.0 | n/a |
| Digital Twin Registry | digital-twin-registry:0.10.0 | 0.10.0 | #1536 |
| Golden Record Business Partner Number (BPN) Service | bpdm: 6.2.0 | 7.2.0 | #1539 |
| Industry Core Hub | industry-core-hub:0.4.0 | v0.4.0 | #1532 |
| Industry Core KIT | n/a | 1.5.0 | n/a |
| PURIS | puris: 5.1.1 | 4.1.1 | #1538 |
| Self Description (SD) Factory | sdfactory: 2.1.35 | 2.1.26 | #1537 |
| Tractus-X Software Development KIT (SDK) | n/a | v0.6.1 | #1533 |
- All not listed products and KITs have not been updated and are based on the release 25.09 or previous releases
- These products were not part of the testing phase
- 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, 25.03, 25.06, 25.09 and 25.12. Without implementing this interim solution, participants will not be able to fully utilize this release in consequence.
- For E2E Testing, the 2.2.3 of the SSI DIM Middle Layer was used - this component is FOSS but the currently used wallet (see previous item) is not
- Complete EcoPass functionality completely included on this release (only creation of passports in a Catalog Part)
- It will be released on a beta tag from the PR
- One defect was found at the E2E test phase, when creating a serialized part, the "partInstanceId" field is obligatory, but if you leave it empty, it will create the part with it empty (which is not a blocker, just you will not be able to search by partInstanceId, since it is not specified): for more infomration
- PURIS FOSS has not been integrated with Tractus-X Connector 0.11.x and new Policy Profile (CX25.09)
- Rest see, Changelog, Known Knows
- Compatibility with EDC 0.11.x (Saturn) not tested completely see here
The following runtime has been used during end-to-end test:
- Kubernetes version:
1.33.1 - Applications used
- PostgreSQL version:
15.4.0or higher - DTR version 0.10.0
- PostgreSQL version:
:::note
Tractus-X Connector has been tested on both Postgresql versions: 15.x and 16.x
:::
You can search all released helm charts with the following commands:
helm repo add tractusx-dev https://eclipse-tractusx.github.io/charts/dev
helm repo update tractusx-dev
helm search repo tractusx-dev --versionsThe official Bitnami Helm chart repository has been deprecated or is no longer maintained in its previous location. Bitnami has migrated legacy
container images to a new repository called bitnamilegacy. Helm charts using Bitnami container images must be updated to reference this new source
to ensure continued functionality. With bitnamilegacy we won’t receive security updates.
:::tip
If you are using a provided helm chart from Eclipse Tractus-X that uses Bitnami container images and it doesn't work, please check the values.yaml file of the respective chart
and update/overwrite the image repository from bitnami/<image-name> to bitnamilegacy/<image-name>.
:::
Extract from values.yaml:
postgresql:
image:
# -- workaround to use bitnamilegacy chart
repository: bitnamilegacy/postgresql
tag: 15.4.0-debian-11-r45:::tip
For installation details, please see the referenced Repositories / Releases and related documentation (e.g. migration documentation)
:::
Our community and results/releases depends on our contributors. We want to thank everyone who has contributed to this release by reporting issues, discussing solutions, writing code, or reviewing contributions.
:::note
The above list contains all contributors and committers that have been involved in this release. The list is generated automatically based on the amount of contributions to the repositories of the Eclipse Tractus-X organization on GitHub.
It's not only about code contributions, but also about reporting issues, discussing solutions, writing documentation, or reviewing contributions.
:::
:::note
The planned and implemented features can be found in the sig-release issue list (filtered by milestone 25.09). These features describe only the requested new function/functionality.
Most of the features are linked to product specific issues. Please have a look on product specific repositories for detailed information on the product specific issues tabs.
:::
| Component | Helm Chart (s) | App-/KIT Version (s) | Release Check |
|---|---|---|---|
| Data Trust & Security KIT | n/a | 0.0.1 | #1495 |
| Requirement KIT | n/a | 0.1.0 |
:::note
- The product
Release Checksissues for each product have been updated to reflect the new versions of the components included in this release. Please refer to these issues for detailed information on the updates. - The KITs
Release Checksissues were also updated.
:::
| Component | Helm Chart (s) | App-/KIT Version (s) | Release Check |
|---|---|---|---|
| Business Partner KIT | n/a | 10.0.0 | #1487 |
| BPN DID Resolution Service (BDRS) | bdrs: 0.5.7 | 0.5.7 | #1454 |
| Demand and Capacity Management KIT | n/a | 1.4.0 | #1264 |
| Digital Twin Registry | digital-twin-registry:0.9.0 | 0.9.0 | #1458 |
| Tractus-X Connector (Eclipse Dataspace Components Connector) | tractusx-connector: 0.11.0 | 0.11.0 | #1453 |
| Golden Record Business Partner Number (BPN) Service | bpdm: 6.1.0 | 7.1.0 | #1463 |
| Identity and Access Management (IAM) | centralidp: 4.2.1 sharedidp: 4.2.1 |
keycloak: 25.0.6 | #1459 |
| Industry Core Hub | industry-core-hub:0.3.0 | v0.2.0 | #1456 |
| Portal | portal: 2.6.0 | registration: 2.2.2 frontend: 2.6.0 backend: 2.6.0 assets: 2.6.0 |
#1459 |
| Product Carbon Footprint KIT | n/a | 1.3.0 | |
| PURIS | puris: 4.1.1 | 3.3.0 | #1448 |
| PURIS KIT | n/a | 0.4.0 | #1494 |
| Self Description (SD) Factory | sdfactory: 2.1.34 | 2.1.25 | #1466 |
| Supply Chain Disruption Notification KIT | n/a | 2.0.0 | #1480 |
| Tractus-X Software Development KIT (SDK) | n/a | v0.5.0 | #1457 |
| Traceability KIT | n/a | 7.0.0 |
- All not listed products and KITs have not been updated and are based on the release 25.06
- These products were not part of the testing phase
- 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, 25.03, 25.06 and 25.09. Without implementing this interim solution, participants will not be able to fully utilize this release in consequence.
- For E2E Testing, the 2.2.3 of the SSI DIM Middle Layer was used - this component is FOSS but the currently used wallet (see previous item) is not
- When creating a marketplace app the Portal does not support an internal technical user profile for BPDM permission group Gate Input Consumer. Therefore, it is currently not possible to create a marketplace app that enables access to ReadAccessGateInputForSharingMember offers for external VAT services wanting to access sharing member Gates
- For the new Tractus-X Connector 0.11 the golden record process was only tested on the 3rd release candidate, not the actual released version. There were no backwards compatibility tests between older Tractus-X Connector versions and the new Tractus-X Connector 0.11.
- BPDM currently only offers documentation on how to use the Tractus-X Connector 0.11 over DCP 1.0. There are no tutorials for DCP 0.8 available.
- Beware of the changes in the acceptable policies, which inflict breaking changes required by services that create new policies -- see migration guide for more information.
- Policy right operands given as array are not returned as specified, they work, but the returned right operand is a string representation of the json object(#2221)
- DCP implementation uses a wrong property name. SAP DIM is capable to deal with the wrong property name (#2255)
- Application of policies that can be ensured automatically not complete (#2259)
- There is a complex issue about the compatibility of policies with dsp versions, especially regarding backward compatibility (#2288). The issue requires further investigation which we will execute to separate misbehavior from documentation issues.
- RLock is blocking other API calls when negotiation is not successful at the Discovery: industry-core-hub#334
- Trivy scan fails to complete successfully because of alpine version: industry-core-hub#319
- When the Tractus-X Connector restarts, the Connector assets are not recreated for the already available twins: industry-core-hub#318
- Incompatible with Tractus-X Connector
0.11.x:(additional)- Not compliant to CX-0018, due to NOT evaluating the dspace endpoint.
- Not compliant to CX-0152, due to NOT implementing the new odrl profile.
- No authentication is implemented (it will be included in R25.12, PR is ready): industry-core-hub#254
- Data Assets and DTR not covered in migrations
- Data Sovereignty is not transparent to end-users
- Catalog and Negotiations have bad user experience (no actions, no filters)
- Incompatible with Tractus-X Connector
0.11.x:(additional)- Not tested with Tractus-X Connector in version
0.11.x - Not compliant to CX-0018, due to NOT evaluating the dspace endpoint.
- Not compliant to CX-0152, due to NOT implementing the new odrl profile.
- Not tested with Tractus-X Connector in version
- Compatibility with Tractus-X Connector 0.11.x (Saturn) not tested completely: tractusx-sdk#159
- The Saturn APIs were implemented but were not able to be tested because of different bugs found at the connector and due to missing documentation on how to adopt it.
The following runtime has been used during end-to-end test:
- Kubernetes version:
1.29.10 - Applications used
- PostgreSQL version:
15.4.0or more specifically15.4.0-debian-11-r45 - Tractus-X Connector version 0.11.0
- DTR version 0.9.0
- PostgreSQL version:
:::note
Tractus-X Connector has been tested on both Postgresql versions: 15.x and 16.x
:::
You can search all released helm charts with the following commands:
helm repo add tractusx-dev https://eclipse-tractusx.github.io/charts/dev
helm repo update tractusx-dev
helm search repo tractusx-dev --versionsThe official Bitnami Helm chart repository has been deprecated or is no longer maintained in its previous location. Bitnami has migrated legacy
container images to a new repository called bitnamilegacy. Helm charts using Bitnami container images must be updated to reference this new source
to ensure continued functionality. With bitnamilegacy we won’t receive security updates.
:::tip
If you are using a provided helm chart from Eclipse Tractus-X that uses Bitnami container images and it doesn't work, please check the values.yaml file of the respective chart
and update/overwrite the image repository from bitnami/<image-name> to bitnamilegacy/<image-name>.
:::
Extract from values.yaml:
postgresql:
image:
# -- workaround to use bitnamilegacy chart
repository: bitnamilegacy/postgresql
tag: 15.4.0-debian-11-r45:::tip
For installation details, please see the referenced Repositories / Releases and related documentation (e.g. migration documentation)
:::
Implemented features can be found here
| Component | Helm Chart (s) | App-/KIT Version (s) |
|---|---|---|
| Eclipse Tractus-X Software Development KIT (SDK) | n/a | v0.0.7 |
| Industry Core Hub | industry-core-hub:0.2.1 | v0.1.0 |
| Component | Helm Chart (s) | App-/KIT Version (s) |
|---|---|---|
| Business Partner KIT | n/a | 9.0.0 |
| Digital Twin Registry | digital-twin-registry:0.8.0 | 0.8.0 |
| Eclipse Data Space Connector (Tractus-X EDC) | tractusx-connector: 0.10.0 | 0.10.0 |
| Golden Record Business Partner Number (BPN) Service | bpdm: 6.0.0 | 7.0.0 |
| Identity and Access Management (IAM) | centralidp: 4.2.0 sharedidp: 4.2.0 |
keycloak: 25.0.6 |
| Item Relationship Service (IRS) | item-relationship-service: 9.0.0 | 7.0.1 |
| Policy Hub | policy-hub: 1.3.1 | 1.3.1 |
| Portal | portal: 2.5.0 | registration: 2.2.1 frontend: 2.5.0 backend: 2.5.0 assets: 2.5.0 |
| PURIS | puris: 3.0.1 | 3.1.0 |
| Self Description (SD) Factory | sdfactory: 2.1.33 | 2.1.24 |
| SSI Authority & Schema Registry | ssi-asr: 2.0.0 | 2.0.0 |
| SSI Credential Issuer | ssi-credential-issuer: 1.4.0 | 1.4.0 |
| Supply Chain Disruption Notification KIT | n/a | 2.0.0 |
| Trace-X Traceability Application | traceability-foss: 1.4.3 | 15.0.1 |
| Traceability KIT | n/a | 6.1.0 |
- All not listed products and KITs have not been updated and are based on the release 25.03
- These products were not part of the e2e testing phase
- And are not tested with the current EDC version 0.10.0 and the current DTR version 0.8.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, 25.03 and 25.06. Without implementing this interim solution, participants will not be able to fully utilize this release in consequence.
- For E2E Testing, the 2.2.3 of the SSI DIM Middle Layer was used - this component is FOSS but the currently used wallet (see previous item) is not
- When creating a marketplace app the Portal does not support an internal technical user profile for BPDM permission group Gate Input Consumer. Therefore, it is currently not possible to create a marketplace app that enables access to ReadAccessGateInputForSharingMember offers for external VAT services wanting to access sharing member Gates
- No Authentication at the backend & frontend provided see here
- No profile & settings provided at frontend (just a mock) see here
- Part Instance twins not included in scope (not supported in backend, and mocked in the frontend) see here
- Not submodel is displayed in the frontend, also is not possible to create submodels see here
- No display of aspect models in frontend. (PCF and other data models are not supported, just PartTypeInformation v1.0.0) see here
- It is not possible to unshare once shared see here
- Persistent submodel service needed for end-to-end stability see here
- Connector URL: Updating connector URL for connectors with missing SD Document is not working see here
- for comprehensive list see here
- Auto-setup feature for App Subscriptions: validation is triggered on opening pop up see here
- for comprehensive list see here
- EDC Version specified is v0_9_0 but works with v0.10.0 see here
- EDC Service has not factory method. see here
- The "Show Details Table" function is non-functional in the as Planned view see here
- Record Information is Visible for asPlanned Parts to Users with Supervisor Role (only role Admin shold be permitted) see here
- Insufficient visualization of Teaction Battery Code see here
The following runtime has been used during end-to-end test:
- Kubernetes version:
1.29.10 - Applications used
- PostgreSQL version:
15.4.0or more specifically15.4.0-debian-11-r45 - EDC version 0.10.0
- DTR version 0.8.0
- PostgreSQL version:
Note: Tractus-X EDC has been tested on both Postgresql versions: 15.x and 16.x
You can search all released helm charts with the following commands:
helm repo add tractusx-dev https://eclipse-tractusx.github.io/charts/dev
helm repo update tractusx-dev
helm search repo tractusx-dev --versionsFor installation details, please see the referenced Repositories / Releases.
Implemented features can be found here
| Component | Helm Chart (s) | App-/KIT Version (s) |
|---|---|---|
| Logistics KIT | n/a | 1.0.0 |
| Customs KIT | n/a | 1.0.0 |
| Component | Helm Chart (s) | App-/KIT Version (s) |
|---|---|---|
| Knowledge Agents | remoting-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.1 | v4.0.1 |
- 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
- 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 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 (DPP) will be not part of the release
- Knowledge Agents is not part of this release but was tested with the EDC release candidate 0.8.0-RC4
- 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
- on Kubernetes versions:
1.29.10 - with PostgreSQL versions:
15.4.0.or more specific15.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
You can search all released helm charts with the following commands:
helm repo add tractusx-dev https://eclipse-tractusx.github.io/charts/dev
helm repo update tractusx-dev
helm search repo tractusx-dev --versionsFor installation details, please see the referenced Repositories / Releases.
Implemented features can be found here
- All not listed products and KITs have not been updated and are based on the release 24.08
- These products were not part of the e2e testing phase
- And are not tested with the current EDC version 0.8.0
- BPN DID Resolution Service (BDRS) is unchanged but was part of the testing phase
- PURIS is unchanged but regression tests were executed
- Knowledge Agents was updated to version 0.8.0 but only tested with the EDC release candidate 0.8.0-RC4
- This Tractus-X release does not include a Managed Identity Wallet (MIW). The development team decided on a temporary bridging solution, based on a commercial application, to test and ship Release 24.08. Without implementing this interim solution, participants will not be able to fully utilize this Tractus-X release in consequence.
- For E2E Testing, the 2.1.1 of the SSI DIM Middle Layer was used - this component is FOSS but the currently used wallet (see previous item) is not.
- Security concern about exposed technical users when subscribing BPDM services over the Portal -> see according issue
- 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
The release has been tested
- on Kubernetes versions:
1.28.9 - with PostgreSQL versions:
15.2.1.
Note: Tractus-X EDC has been tested on both Postgresql versions: 15.x and 16.x
You can search all released helm charts with the following commands:
helm repo add tractusx-dev https://eclipse-tractusx.github.io/charts/dev
helm repo update tractusx-dev
helm search repo tractusx-dev --versionsFor installation details, please see the referenced Repositories / Releases.
| Component | Helm Chart (s) | App-/KIT Version (s) |
|---|---|---|
| Knowledge Agents AAS Bridge | aas-bridge: 1.13.7 | 1.13.7 |
| Supply Chain Disruption Notifications Kit | n/a | 1.0.0 |
| SSI Authority & Schema Registry | ssi-asr: 1.0.0 | 1.0.0 |
| Component | Helm Chart (s) | App-/KIT Version (s) |
|---|---|---|
| Country Risk | country-risk: 4.0.2 | 1.3.1 |
| Component | Helm Chart (s) | App-/KIT Version (s) |
|---|---|---|
| Managed Identity Wallet (MIW) | managed-identity-wallet: 0.5.0 | v0.5.0 |
:::note For known knowns of unchanged/untested components, please refer to previous changelog(s) :::
- Relevant components and interfaces developed considering Gaia-X Trust Framework - 22.10
- Connection to an external Clearing House service for the entire Catena-X ecosystem is required. The Gaia-X compliance service should generally be capable of recognizing all companies that are able to register with the Catena-X Portal.
- This Tractus-X release does not include a Managed Identity Wallet (MIW). The development team decided on a temporary bridging solution, based on a commercial application, to test and ship Release 24.08. Without implementing this interim solution, participants will not be able to fully utilize this Tractus-X release in consequence.
- For E2E Testing, the 1.2.0 of the SSI DIM Middle Layer was used - this component is FOSS but the currently used wallet (see previous item) is not.
- Documentation content (e.g. architecture, manuals etc) and folder structure have not explicitly been checked for this Release, as relevant TRGs are not yet in force. The vast majority of components are evolutions of previous Releases, with a thorough review undergone. This leads to a high confidence in the quality of existing documentation within the product repositories.
- FOSS components developed and pre-tested to TRL6 with artificial test data only
- No crosscheck of functionality in verification environment
- No execution of Load-, Performance- or Penetration Tests
- No assignment of Export Control Classification Numbers (ECCN) to FOSS components
- GeoBlocking recommended for Operations (GBaaS)
- Security concept (overall) recommended for Operations
- Listed components in "Unchanged, untested" category were not verified in combination with the current release package and are only compatible with Catena-X standards as specified. Use at your own risk at this time.
- Listed components in "Incompatible" category are not compatible with the current release package and the latest standards.
- BPDM has some Known Knowns regarding Portal integration listed in detail here
- BPDM standard configuration not compatible with Portal's Central-IDP configuration
- Portal's Partner Network page does not currently show business partner member data due to an authorization issue
- Currently not possible to add company's site and address business partners over the Portal due to authorization issue
- Security concern about exposed technical users when subscribing BPDM services over the Portal
- DTR introduces the DTR-EDC Access Control extension. The goal of this EDC extension is to enforce authorized access to submodel implementations according to AAS and Catena-X concluded contracts. It is a Maven artifact that can be used for building their own EDC dataplane image with the extension. For more details, see here.
The release has been tested
- on Kubernetes versions:
1.28.9 - with PostgreSQL versions:
15
Note: Tractus-X EDC has been tested on both Postgresql versions: 15.x and 16.x
You can search all released helm charts with the following commands:
helm repo add tractusx-dev https://eclipse-tractusx.github.io/charts/dev
helm repo update tractusx-dev
helm search repo tractusx-dev --versionsFor installation details, please see the referenced Repositories / Releases.
| Component | Helm Chart (s) | App-/KIT Version (s) |
|---|---|---|
| Behaviour Twin KIT | n/a | 1.0.0 |
| BPN DID Resolution Service (BDRS) | bdrs: 0.0.4 | 0.0.4 |
| PURIS KIT | n/a | 0.2.0 |
| SSI Credential Issuer | ssi-credential-issuer: 1.0.0 | 1.0.0 |
| Component | Helm Chart (s) | App-/KIT Version (s) |
|---|---|---|
| Data Governance KIT | n/a | 0.1.0 |
| Managed Identity Wallet (MIW) | managed-identity-wallet: 0.3.0 | 0.3.0 |
| OSim KIT | n/a | 2.0.0 |
| Component | Helm Chart (s) | App-/KIT Version (s) |
|---|---|---|
| Behavioral Twin: Health Indicators (HI) KIT | n/a | 0.1.1 |
| Behavioral Twin: Remaining useful Life (RUL) KIT | n/a | 0.1.1 |
| Certificate Management KIT | n/a | 0.1.0 |
- Relevant components and interfaces developed considering Gaia-X Trust Framework - 22.10
- Connection to an external Clearing House service for the entire Catena-X ecosystem is required. The Gaia-X compliance service should generally be capable of recognizing all companies that are able to register with the Catena-X Portal.
- Conformity to Asset Administration Shell (AAS) API v3.0 and bugfix v3.0.1 is given. Fine granular access control introduced for optional use.
- This Tractus-X release does not include a Managed Identity Wallet (MIW). The development team decided on a temporary bridging solution, based on a commercial application, to test and ship Release 24.05. Without implementing this interim solution, participants will not be able to fully utilize this Tractus-X release in consequence. An updated and validated version of MIW is expected in Release 24.08.
- The Tractus-X EDC has undergone significant changes in its Management API, communication with external services and internal APIs.
- Documentation content (e.g. architecture, manuals etc) and folder structure have not explicitly been checked for this Release, as relevant TRGs are not yet in force. The vast majority of components are evolutions of previous Releases, with a thorough review undergone. This leads to a high confidence in the quality of existing documentation within the product repositories.
- FOSS components developed and pre-tested to TRL6 with artificial test data only
- No crosscheck of functionality in verification environment
- No execution of Load-, Performance- or Penetration Tests
- No assignment of Export Control Classification Numbers (ECCN) to FOSS components
- GeoBlocking recommended for Operations (GBaaS)
- Security concept (overall) recommended for Operations
- Listed components in "Unchanged, untested" category were not verified in combination with the current Release package and are only compatible with Catena-X Standards as specified. Use at your own risk at this time.
The release has been tested
- on Kubernetes versions:
1.27.3 - with PostgreSQL versions:
15
Note: Tractus-X EDC has been tested on both Postgresql versions: 15.x and 16.x
The following violations of TRG 5.07 apply:
- Golden Record Business Partner Number (BPN) Service operates on Postgresql version 16.x (not 15), but has been successfully tested for the current Release
- Country Risk deploys a Postgresql version 15 per helm chart. Yet, the test has been successfully performed on version 14.x.
You can search all released helm charts with the following commands:
helm repo add tractusx-dev https://eclipse-tractusx.github.io/charts/dev
helm repo update tractusx-dev
helm search repo tractusx-dev --versionsFor installation details, please see the referenced Repositories / Releases.
| Component | Helm Chart (s) | App-/KIT Version (s) |
|---|---|---|
| Certificate Management KIT | n/a | 0.1.0 |
| Data Governance KIT | n/a | 0.1.0 |
| Environmental and Social Standards (ESS) KIT | n/a | 0.1.0 |
| Industry Core KIT | n/a | 0.1.0 |
| Manufacturing as a Service (MaaS) KIT | n/a | 0.1.0 |
| PURIS | puris: 1.0.0 | 1.0.0 |
| Component | Helm Chart (s) | App-/KIT Version (s) |
|---|---|---|
| Behavioral Twin: Health Indicators (HI) KIT | n/a | 0.1.1 |
| Behavioral Twin: Model and Data processing (MDP) KIT | n/a | 0.1.1 |
| Behavioral Twin: Remaining useful Life (RUL) KIT | n/a | 0.1.1 |
| Circularity KIT | n/a | 0.2.0 |
| Modular Production KIT | n/a | 0.1.0 |
-
Relevant components and interfaces developed considering Gaia-X Trust Framework - 22.10
-
Connection to an external Clearing House service for the entire Catena-X ecosystem is required. The Gaia-X compliance service should generally be capable of recognizing all companies that are able to register with the Catena-X Portal.
-
Conformity to Asset Administration Shell v3.0, API live example (AAS) is given. The DTR “/query” interface is finally deprecated and no longer available with this Release as announced. Details can be found in the changelog of the respective component.
-
EDC provides no new release compared to 23.12 but only patches: EDC version 0.5.4 is part of 24.03 with the following limitations: Standard Security Tests have been performed, but it is strongly recommended for each EDC operator to apply own security measures. Especially the Dynamic Application Security Testing (DAST) needs to be executed for each specific operation environment and instance. Tractus-X release guidelines (TRGs) have been fulfilled.
-
FOSS components developed and pre-tested to TRL6 with artificial test data only
-
No crosscheck of functionality in verification environment
-
No execution of Load-, Performance- or Penetration Tests
-
No assignment of Export Control Classification Numbers (ECCN) to FOSS components
-
GeoBlocking recommended for Operations (GBaaS)
-
Security concept (overall) recommended for Operations
-
Listed components in "Unchanged, untested" category were not verified in combination with the current Release package and are only compatible with Catena-X Standards as specified. Use at your own risk at this time.
- Tested on Kubernetes versions:
1.27.3 - Tested with PostgreSQL versions:
15-
Three exceptions apply for
- Golden Record Business Partner Number (BPN) Service
- Managed Identity Wallet (MIW)
- Managed Service Orchestrator (MSO)
Those components violate TRG 5.07 as they still operate on Postgresql DB Version 14.x (not 15), but have been successfully tested for the current Release.
-
You can search all released helm charts with the following commands:
helm repo add tractusx-dev https://eclipse-tractusx.github.io/charts/dev
helm repo update tractusx-dev
helm search repo tractusx-dev --versionsFor installation details, please see the referenced Repositories / Releases.
| Component | Helm Chart (s) | App-/KIT Version (s) |
|---|---|---|
| Behavioral Twin: Health Indicators (HI) KIT | n/a | 0.1.0 |
| Behavioral Twin: Model and Data processing (MDP) KIT | n/a | 0.1.0 |
| Circularity KIT | n/a | 0.1.0 |
| Demand and Capacity Management (DCM) KIT | n/a | 3.1.0 |
| Knowledge Agent KIT | n/a | 1.0.0 |
| Modular Production KIT | n/a | 0.1.0 |
| Component | Helm Chart (s) | App-/KIT Version (s) |
|---|---|---|
| BPN Discovery | bpndiscovery: 0.1.12 | 0.2.6 |
| Business Partner KIT | n/a | 3.0.0 |
| Connector KIT | n/a | 0.6.0 |
| Country Risk | country-risk: 3.0.6 | Frontend: v1.3.0 Backend: v1.2.3 |
| Digital Twin KIT | n/a | 1.1.0 |
| Digital Twin Registry | registry: 0.3.19 | v0.3.19 |
| Golden Record Business Partner Number (BPN) Service | bpdm: 3.1.2 | v4.1.0 |
| Item Relationship Service (IRS) | irs-helm: 6.9.1 | 4.0.1 |
| Knowledge Agents | remoting-agent: 1.10.15 | 1.10.15 |
| Managed Identity Wallet (MIW) | managed-identity-wallet: 0.3.0 | 0.3.0 |
| Managed Service Orchestrator | managed-service-orchestrator: 1.5.1 | v1.5.1 |
| Portal | portal: 1.7.0 | Registration: v1.5.4 Frontend: v1.7.0 Backend: v1.7.0 Assets: v1.7.0 |
| Quality KIT | n/a | 1.1.0 |
| Self Description (SD) Factory | sdfactory: 2.1.8 | v2.1.7 |
| Semantic Hub | semantic-hub: 0.1.31 | v0.2.14 |
| Simple Data Exchanger (SDE) | sde: 0.1.3 | Frontend: v2.3.3 Backend: v2.3.3 |
| Trace-X Traceability Application | 1.3.20 | 9.0.0 |
| Traceability KIT | n/a | 3.0.0 |
All components listed here have not seen any update since their previous Release. No specific regression tests executed.
| Component | Helm Chart (s) | App-/KIT Version (s) |
|---|---|---|
| Data Chain KIT | n/a | 1.1.0 |
| Digital Product Pass | digital-product-pass: v1.0.1 | v1.0.1 |
| Discovery Finder | discoveryfinder: 0.1.11 | v0.2.4-M1 |
| Eclipse Data Space Connector (EDC) | tractusx-connector: 0.5.3 | 0.5.3 |
| Eco Pass KIT | n/a | 0.1.0 |
| OSim KIT | n/a | 1.0.0 |
| Product Carbon Footprint (PCF) KIT | n/a | 0.1.0 |
| Behavioral Twin: Remaining useful Life (RUL) KIT | n/a | 0.1.1 |
- Relevant components and interfaces developed considering Gaia-X Trust Framework - 22.10
Connection to an external Clearing House service for the entire Catena-X ecosystem is required. The Gaia-X compliance service should generally be capable of recognizing all companies that are able to register with the Catena-X Portal. - Conformity to Asset Administration Shell v3.0, API live example (AAS) is given. For compatibility reasons, the deprecated DTR query interface “/query” will additionally be supported until Q1/2024. Details can be found in the changelog of the respective component.
- EDC provides no new release compared to 23.09 but only patches: EDC version 0.5.3 is part of 23.12 with the following limitations:
Standard Security Tests have been performed, but it is strongly recommended for each EDC operator to apply own security measures. Especially the Dynamic Application Security Testing (DAST) needs to be executed for each specific operation environment and instance.
Tractus-X release guidelines (TRGs) 5.11, 7.01, 7.05 and 7.07 had not been fulfilled with v0.5.3. All of those are now addressed from 0.6.0-rc2 on. - MIW interim version 0.2.0 had passed functional E2E-testing within boundaries of the Catena-X consortia, but faced severe Security issues. MIW version 0.3.0 as part of the current Release package addresses all known Security issues, but did explicitly not undergo any functional E2E-testing (again).
- FOSS components developed and pre-tested to TRL6 with artificial test data only
- No crosscheck of functionality in verification environment
- No execution of Load-, Performance- or Penetration Tests
- No assignment of Export Control Classification Numbers (ECCN) to FOSS components
- GeoBlocking recommended for Operations (GBaaS)
- Security concept (overall) recommended for Operations
- Tested on Kubernetes versions:
1.27.3 - Tested with PostgreSQL versions:
15
You can search all released helm charts with the following commands:
helm repo add tractusx-dev https://eclipse-tractusx.github.io/charts/dev
helm repo update tractusx-dev
helm search repo tractusx-dev --versionsFor installation details, please see the referenced Repositories / Releases.
Tractus-X has switched to YY.0M.MICRO Calendar Versioning for overarching, quarterly Releases. Therefore, the previous working title of Release 23.09 was 3.2.0. Semantic Versioning remains unchanged for all components.
| Component | Helm Chart (s) | App Version (s) |
|---|---|---|
| Behavioral Twin: Remaining useful Life (RUL) KIT | n/a | 0.1.1 |
| BPN Discovery | bpndiscovery: 0.1.11 | 0.2.5-M1 |
| Digital Twin KIT | n/a | 1.0.0 |
| Discovery Finder | discoveryfinder: 0.1.11 | v0.2.4-M1 |
| Eco Pass KIT | n/a | 0.1.0 |
| Knowledge Agents | remoting-agent: 1.9.8 | 1.9.8 |
| OSim KIT | n/a | 1.0.0 |
| PCF KIT | n/a | 0.1.0 |
| Quality KIT | n/a | 0.1.0 |
| Component | Helm Chart (s) | App Version (s) |
|---|---|---|
| Business Partner KIT | n/a | 2.0.0 |
| Connector KIT | n/a | 0.5.0 |
| Data Chain KIT | n/a | 1.1.0 |
| Digital Product Pass | digital-product-pass: v1.0.1 | v1.0.1 |
| Digital Twin Registry | registry: 0.3.24 | v0.3.16-M1 |
| Eclipse Data Space Connector (EDC) | tractusx-connector: 0.5.1 | 0.5.1 |
| Golden Record Business Partner Number (BPN) Service | bpdm: 3.0.4 | v4.0.1 |
| Item Relationship Service (IRS) | irs-helm: 6.4.2 | 3.3.4 |
| Managed Identity Wallet (MIW) | managed-identity-wallet: 0.1.0 | 0.1.0 |
| Managed Service Orchestrator (Renamed from Autosetup Service) |
managed-service-orchestrator: 1.5.0 | 1.5.0 |
| Portal | portal: 1.6.0 | Registration: v1.5.0 Frontend: v1.6.0 Backend: v1.6.0 Assets: v1.6.0 |
| Self Description (SD) Factory | sdfactory: 2.1.7 | v2.1.6 |
| Semantic Hub | semantic-hub: 0.1.29 | v0.2.11-M1 |
| Simple Data Exchanger (SDE) | sde: 0.0.9 | Frontend: v2.1.1 Backend: v2.1.1 |
| Trace-X Traceability Application | 1.3.12 | 6.0.0 |
| Component | Helm Chart (s) | App Version (s) |
|---|---|---|
| Country Risk | country-risk: 1.0.0 | Frontend: v1.1.2 Backend: v1.1.1 |
| Traceability KIT | n/a | 1.0.1 |
| Component |
|---|
| DAPS Registration Service |
| Dynamic Attribute Provisioning Service (DAPS) |
- Relevant components and interfaces developed considering Gaia-X Trust Framework - 22.10
Connection to an external Clearing House service for the entire Catena-X ecosystem is required. The Gaia-X compliance service should generally be capable of recognizing all companies that are able to register with the Catena-X Portal. - Conformity to Asset Administration Shell v3.0, API live example (AAS) is given. For compatibility reasons, an older version of the DTR query interface “/query” will additionally be supported until the end of 2023. Details can be found in the changelog of the respective component.
- Country Risk was not verified in combination with the current Release package. Use at your own risk. The component will either be deprecated or fully re-integrated in the next Release.
- Traceability KIT was not verified in combination with the current Release package and is only compatible with Catena-X Standards as specified. Use at your own risk at this time, but expect an updated KIT version shortly.
- FOSS components developed and pre-tested to TRL6 with artificial test data only
- No crosscheck of functionality in verification environment (STABLE, Pre-PROD)
- No execution of Load-, Performance- or Penetration Tests
- No assignment of Export Control Classification Numbers (ECCN) to FOSS components
- GeoBlocking recommended for Operations (GBaaS)
- Security concept (overall) recommended for Operations
- Tested on Kubernetes versions:
1.25.6 - Tested with PostgreSQL versions:
15
You can search all released helm charts with the following commands:
helm repo add tractusx-dev https://eclipse-tractusx.github.io/charts/dev
helm repo update tractusx-dev
helm search repo tractusx-dev --versionsFor installation details, please see the referenced Repositories / Releases.
| Component | Helm Chart (s) | App Version (s) |
|---|---|---|
| Traceability KIT | n/a | 1.0.1 |
- n/a
| Component | Helm Chart (s) | App Version (s) |
|---|---|---|
| Autosetup Service | autosetup: 1.2.7 | 1.2.7 |
| Connector KIT | n/a | 1.2.0 |
| Country Risk | country-risk: 1.0.0 | Frontend: v1.1.2 Backend: v1.1.1 |
| DAPS Registration Service | daps-reg-service: 2.0.7 | 2.0.7 |
| Digital Twin Registry | registry: 0.2.17 | 0.2.0-M12-multi-tenancy |
| Dynamic Attribute Provisioning Service (DAPS) | daps-server: 1.7.9 | v1.7.9 |
| Eclipse Data Space Connector (EDC) | tractusx-connector: 0.3.4 tractusx-connector-azure-vault: 0.3.4 tractusx-connector-memory: 0.3.4 |
0.3.4 |
| Golden Record Business Partner Number (BPN) Service | bpdm-gate: 3.3.1 bpdm-pool: 4.3.1 |
v3.2.2 |
| Item Relationship Service (IRS) | irs-helm: 5.0.10 | 2.4.1 |
| Portal | portal: 1.3.0 | Registration: v1.3.0 Frontend: v1.3.0 Backend: v1.3.0 Assets: v1.3.0 |
| Self Description (SD) Factory | sdfactory: 2.0.8 | 2.0.8 |
| Semantic Hub | semantic-hub: v0.1.19 | 0.2.6-M1 |
| Simple Data Exchanger (SDE) | dftfrontend: 2.0.0 dftbackend: 2.0.0 |
Frontend: 2.0.0 Backend: 2.0.0 |
| Trace-X Traceability Application | 1.3.5 | 3.1.2 |
| Component | Helm Chart (s) | App Version (s) |
|---|---|---|
| Business Partner KIT | n/a | 1.0.0 |
| Data Chain KIT | n/a | 1.0.0 |
| Digital Product Pass | consumer-backend: 0.2.5 consumer-ui: 0.2.5 |
0.4.6 |
| Managed Identity Wallet (MIW) | managed-identity-wallets 0.7.5 | v3.3.2 |
- Relevant components and interfaces developed considering Gaia-X Trust Framework - 22.10 Connection to an external Clearing House service for the entire Catena-X ecosystem required. The Gaia-X compliance service should generally be capable to recognize all companies that are able to register with the Catena-X Portal.
- FOSS components developed and pre-tested to TRL6 with artificial test data only
- No crosscheck of functionality in verification environment (Pre-PROD)
- No execution of Load-, Performance- or Penetration Tests
- No assignment of Export Control Classification Numbers (ECCN) to FOSS components
- GeoBlocking recommended for Operations (GBaaS)
- Security concept (overall) recommended for Operations
- Managed Identity Wallet (MIW) version 3.3.2 has passed all functional tests with the current Release package; yet this version faces a Security vulnerability with regards to libraries used (CVE-2023-0464, GHSA-fj2w-wfgv-mwq6). These issues have been addressed in MIW version 3.3.3 (no other functional changes); however MIW 3.3.3 is not part of this release.
- Tested on Kubernetes versions:
1.24.6 - Tested with PostgreSQL versions:
14
You can search all released helm charts with the following commands:
helm repo add tractusx-dev https://eclipse-tractusx.github.io/charts/dev
helm repo update tractusx-dev
helm search repo tractusx-dev --versionsFor installation details, please see the referenced Repositories / Releases.
- n/a
| Component | Helm Chart (s) | App Version (s) |
|---|---|---|
| Autosetup Service | autosetup: 1.2.0 | 1.2.0 |
| DAPS Registration Service | daps-reg-service: 2.0.0 | 2.0.0 |
| Component | Helm Chart (s) | App Version (s) |
|---|---|---|
| Simple Data Exchanger (SDE) | dftfrontend: 1.9.0 dftbackend: 1.9.1 |
Frontend: 1.9.0 Backend: 1.9.1 |
- Relevant components and interfaces developed considering Gaia-X Trust Framework - 22.10 Connection to an external Clearing House service for the entire Catena-X ecosystem required. The Gaia-X compliance service should generally be capable to recognize all companies that are able to register with the Catena-X Portal.
- FOSS components developed and pre-tested to TRL6 with artificial test data only
- No crosscheck of functionality in verification environment (Pre-PROD)
- No execution of Load-, Performance- or Penetration Tests
- No assignment of Export Control Classification Numbers (ECCN) to FOSS components
- GeoBlocking recommended for Operations (GBaaS)
- Security concept (overall) recommended for Operations
- Tested on Kubernetes versions:
1.24.6 - Tested with PostgreSQL versions:
14
You can search all released helm charts with the following commands:
helm repo add tractusx-dev https://eclipse-tractusx.github.io/charts/dev
helm repo update tractusx-dev
helm search repo tractusx-dev --versionsFor installation details, please see the referenced Repositories / Releases.
- Connector KIT, v1.0.0
- Business Partner KIT, v1.0.0
- Data Chain KIT, v1.0.0
- Country Risk, Frontend v1.1.0, Backend v1.0.3
- Digital Product Pass, v0.4.6
- Trace-X Traceability Application, v1.1.0
- Autosetup Service, Frontend v1.4.7, Backend v1.4.6
- Digital Twin Registry, v0.2.0-M3-multi-tenancy
- Dynamic Attribute Provisioning Service (DAPS), v1.7.1
- DAPS Registration Service, v1.0.5
- Eclipse Data Space Connector (EDC), v0.1.6
- Golden Record Business Partner Number (BPN) Service, v3.0.3
- Item Relationship Service (IRS), v2.3.0
- Managed Identity Wallet (MIW), v3.3.2
- Portal, v1.0.0 for Registration, Frontend, Backend and Assets
- Self Description (SD) Factory, v2.0.0
- Semantic Hub, v0.1.0-M3
- Relevant components and interfaces developed considering Gaia-X Trust Framework - 22.10
Connection to an external Clearing House service for the entire Catena-X ecosystem required.
The Gaia-X compliance service should generally be capable to recognize all companies that are able to register with the Catena-X Portal. - FOSS components developed and pre-tested to TRL6 with artificial test data only
- No crosscheck of functionality in verification environment (Pre-PROD)
- No execution of Load-, Performance- or Penetration Tests
- No assignment of Export Control Classification Numbers (ECCN) to FOSS components
- GeoBlocking recommended for Operations (GBaaS)
- Security concept (overall) recommended for Operations
- Tested on Kubernetes versions:
1.24.6 - Tested with PostgreSQL versions:
14
- Portal, v0.6.0
- Managed Identity Wallet (MIW), v2.1.0
- Simple Data Exchanger (SDE), v1.7.0
- Autosetup Service, v1.0.1
- DAPS Registration Service, v1.0.5
- Self Description (SD) Factory, v1.0.6
- Semantic Hub, v0.1.0M1
- Item Relationship Service (IRS), v1.3.0
- Developed considering Gaia-X Trust Framework - 22.04
- FOSS components developed and pre-tested to TRL6 with artificial test data only
- Restricted crosscheck of functionality in verification environment:
Smoke-tests did not verify- Approval of company registration
- Mutiple user onboarding
- Registration of EDC and associated SD validations
- IRS
- No execution of Load-, Performance- or Penetration Tests
- No assignment of Export Control Classification Numbers (ECCN) to FOSS components
- GeoBlocking recommended for Operations (GBaaS)
- Tested on Kubernetes versions:
1.24.3 - Tested with PostgreSQL versions:
14
- Eclipse Data Space Connector (EDC), v0.1.2
- Golden Record Business Partner Number (BPN) Service, v2.0.0
- Dynamic Attribute Provisioning Service (DAPS), v1.7.1
- Digital Twin Registry, v0.2.0M2
- FOSS components developed and pre-tested to TRL6 with artificial test data only
- No execution of Load-, Performance- or Penetration Tests
- No assignment of Export Control Classification Numbers (ECCN) to FOSS components
- GeoBlocking recommended for Operations (GBaaS)
- Portal (Registration) as well as Managed Identity Wallet scope required for full functionality; yet both are unreleased at this point in time and can be expected with Release 2.1.0
- Released Helm Chart missing for EDC v0.1.2; can be expected with Release 2.1.0
- Tested on Kubernetes versions:
1.24.3 - Tested with PostgreSQL versions:
14