Beta deployment: Tuesday, November 4th 2025; 4pm-6pm (Berlin time)
PROD deployment: Tuesday, November 25th 2025; 6pm-9pm (Berlin time)
Overview
The Saturn release aligns Cofinity-X components with the latest Tractus-X specifications and evolving Catena-X standards. It introduces key updates that enhance connector compatibility, data exchange stability, and policy management across participating companies.
As the underlying standards and technical specifications have changed, participants are encouraged to contact their respective App or Service Providers to understand how these updates may impact their current configurations or integration timelines.
EDC Compatibility & Upgrade Guidance
Recent Tractus-X release notes (see here) mention complex topics around policy and DSP version compatibility. Below is what this means for Cofinity-X participants:
No immediate upgrade required:
Existing participants using the Jupiter version can continue data exchange seamlessly. There is no need to update to Saturn immediately, and Jupiter will remain supported for at least another year.Gradual migration recommended:
Participants are encouraged to plan upgrades to Saturn during 2026 to ensure alignment with future compatibility and features.App Providers and Enablement Service Providers:
It is a business decision when to release Saturn-compliant stacks. Before participants can upgrade, their respective App Provider must make a Saturn version of the stack available.For Saturn-based participants:
A provider must create separate Contract Definitions for Jupiter and Saturn consumers of the same asset.
Usage policies must align with the schema of each version.
Access policies should always follow the new Saturn rules.
A new Management API endpoint supports correct DSP version handling between Saturn and Jupiter connectors.
For more technical background, refer to the adapted to DSP 2025-01 Tractus-X EDC management walkthrough here.
For more information about Saturn EDC 0.11.x, please consult your EDC provider.
Dataspace OS customers will receive a notification when EDC 0.11.x is released in the application.
What This Means for You
Situation | Action |
You are currently using a Jupiter stack | Continue operations - no change required |
You plan to adopt Saturn soon | Wait for your App/Enablement Provider to release a Saturn-compliant version |
You already operate Saturn components | Ensure Contract Definitions and policies are configured for both Jupiter and Saturn consumers |
You are a Service or App Provider | Plan a Saturn-compliant release during 2026 to stay aligned with ecosystem evolution |
Technical Release Notes Cofinity-X
Portal
New Features:
Connector Management Role for Active Participants
Overview:
To enable dataspace participants (data providers and data consumers) to register their connectors without granting them “Offer Management” rights. The introduction of the Connector Management role ensures that dataspace participants can manage connector registration while maintaining compliance with role-based access.
Enhance Auto-Setup Configuration to Allow App Providers to Define Custom Auth URL, Client ID, and Secret
Overview:
Enable App Providers to configure their own Auth URL, Client ID, and Client Secret for the Auto-Setup process. This enhancement allows the portal backend to authenticate and access each provider’s Auto-Setup URL using their specific credentials
Add Subscription Creation Date and Time in Provided Subscriptions
Overview:
Add a creation date and time field to the Provided Subscriptions section to help users distinguish between multiple subscriptions with the same company name. This enhancement improves clarity and traceability by showing when each subscription was created.
Enable region specific clearinghouse (Backend)
Overview:
Introduce support for region-specific clearinghouses to ensure that transactions and data exchanges are processed according to each region’s requirements. This enhancement allows the system to handle multiple clearinghouses efficiently, improving scalability, localization, and compliance with regional regulations.
Improvements:
Create OWN connector with available Technical user only
I should be able to send only available technical user id in the create connector api i.e in the api POST: /api/administration/connectors/
An error should be thrown if user send the technical user id which is already linked to a connector. Api POST: /api/administration/connectors/ . Error message : 'Techincal user id {userId} is already used by another connector or offer.' Error Type 409
Improve the back button functionality on the Company Subscription page so that it navigates the user to the previously visited screen or page.
Bug Fixes:
We’ve resolved several issues to improve stability and user experience across the Portal:
Company Registration: Corrected hint messages for “CRN” fields, which previously appeared incorrectly for most EU countries and globally.
App Marketplace: Fixed an issue where a blank page appeared when opening an app’s detail view.
Technical User - Connector Management: Restored the missing Connector Management role.
Technical User Management – Connector Profile: Resolved a 409 error that occurred when updating the connector URL.
BP Explorer: Fixed a 403 error on the “Sharing State” API that caused the page to fail loading.
Home Page: Adjusted card alignment issues causing misaligned or overlapping display.
App Access Management: Restored the missing “Select All” checkbox when assigning roles to multiple users.
Connector Registration: Fixed layout issue where the “Connector Type” column was misaligned.
Your Apps: Updated “Load More” button label for consistency (previously shown as “loadmore”).
OSP: Updated “Add Identity Provider” button to use the correct CfxButton component.
Data Test IDs: Added missing data-test IDs for several CTAs to improve test coverage.
IDP, Technical User, Connector Management, and Subscription Pages: Updated CTAs to use the CfxButton component consistently.
BP Explorer – Add Site: Fixed issue where the Submit button remained disabled after address auto-population.
App Subscription (Auto SetUp): Added proper error messages when invalid input data is entered.
Connector Management: Fixed issue where technical users did not reappear after deleting connectors linked to them.
Core Service (Wallet & Credentials)
The Bring Your Own Wallet (BYOW) capability is now fully implemented and functional on the backend, including validation, credential, and DID handling logic.
New Features:
BYOW Portal Backend - Add a controller to validate DID.
Portal Backend - Update DID Documents Endpoints accepts other status.
Issuer Component - DCP Issuance Flow.
Migrating current wallet with enable auto offer flow.
(Keycloak) Added service account for regional clearing house.
Improvements:
BYOW Portal Backend - Add flag to identify user provider to database.
BYOW Portal Backend - Enhance the Credentials BPN logic to BYOW flow.
BYOW Portal Backend - Enhance the membership credential to BYOW flow.
BYOW Portal Backend - Enhance the framework credentials logic to BYOW flow.
Bug Fixes:
Wallet Integration Layer - Adjust general error handler
Wallet Integration Layer - tenant already exist
normalize tenant and technical user names in process retrieval.
Keycloak - Added missing view_app_subscripton and view_service_subscription roles to offer management role to restore access to subscription-related endpoints.
Business Partner Data Management
New Features:
‘IsManagedBy’ Relations - Enhancing Legal Entity Management in BPDM
⚠️ This feature is technically shipping but is pending a legal confirmation process and thus cannot be used ⚠️
🔍 Feature Summary
Enables sharing of hierarchical relationships between legal entities (e.g., subsidiaries and managing companies).
Validates and enriches these relationships via the Golden Record process.
Ensures data integrity by preventing circular or multi-manager assignments.
Allows data space participants to query managed legal entities, their sites, and addresses.
Supports contract negotiation and operational use cases by exposing management relationships.
Differentiates between own company data and managed participant data.
💡 Business Value
Improved Data Governance
Clear ownership and management structures across the data space.
Enables compliance with legal and contractual obligations.
Enhanced Interoperability
Facilitates seamless integration into Catena-X use cases (e.g., traceability, sustainability).
Operational Efficiency
Reduces manual effort in identifying and managing subsidiaries.
Supports automated contract setup and partner onboarding.
Trust & Transparency
Strengthens trust in shared data by validating relationships through the Golden Record process.
"IsOwnedBy" Relationship – Legal Ownership Transparency in BPDM
⚠️ This feature is technically shipping but is pending a legal confirmation process and thus cannot be used ⚠️
🔍 Feature Summary
Goal: Enable CX Data Sharing Members to declare legal ownership structures between BPNLs (legal entities).
Scope:
One-level up/down relationships only.
Only full or majority ownership (no minority stakes).
Shared via Gate Input/Output and stored in CX Pool.
Only 1:1 child-to-parent relationships allowed.
💡 Business Value
Trusted Source: Ownership data comes directly from the data owner, ensuring reliability.
Data Sovereignty: Members control their own legal structure data.
Use Case Enablement:
Consolidated spend reporting
Compliance & financial risk checks
Cost Reduction: Less reliance on external, often unreliable data providers.
BPDM Identifier Limit – Enhancing Data Robustness
🔍 Feature Summary
Goal
Introduces a technical limit per business partner (separately for Legal Entities and Addresses).
Business partners exceeding this limit will be rejected by the Pool with a clear error message.
Ensure technical stability and predictable performance of BPDM by bounding the size of business partner data.
Facilitate easier integration and validation for systems interacting with BPDM.
Scope
Applies only to the Pool component.
Limit: 100 identifiers per Legal Entity and 100 per Address.
Designed to be flexible for future adjustments (e.g., increasing the limit).
💡 Business Value
Improved System Reliability
Bounded data sizes reduce risk of overload and improve system responsiveness.
Simplified Integration
Predictable response sizes make it easier for external systems to consume BPDM data.
Better Validation & Governance
Clear limits enable more robust request validation and error handling.
Scalable Design
Limit is configurable, allowing future adaptation without architectural changes.
Improvements:
BPDM API version change to 7.10
With go-live of Saturn, both Saturn /v7 and Jupiter /v6 endpoints will be available
see swagger here: https://eclipse-tractusx.github.io/api-hub/bpdm/
lifetime of /v6 until release of /v8
v6 is no longer actively developed, no active bugfixing (except critical security)
v6 might profit from backend changes which are common to v6 and v7
EDC Endpoints
EDC Endpoints - Jupiter
Business Partner Explorer
Golden Record
EDC Endpoints - Saturn
Business Partner Explorer
beta: tbc
PROD: tbc
Golden Record
beta: tbc
PROD: tbc
We will continuously update these notes as more information becomes available.
For any questions, please reach out to [email protected]