R24.05 Simple Data Exchanger (SDE) - Release Checks

[ciprianherciu]

[!IMPORTANT]
Follow the guidance on how to use the templates.

Release Info

Please provide information on what you want to be included in the Eclipse Tractus-X release. If you are not owner of this issue, please provide the information as comment to the issue. Make sure to assign this issue to expert(s) for their approval, as soon as you have finished preparation. Multiple assignees allowed; they will un-assign themselves once review completed.

Version to be included in Eclipse Tractus-X release: version placeholder

Leading product repository: repository link

Compliance Verifications

This issue tracks all checks, that need to be performed for a product release in Eclipse Tractus-X.

• [x] Interoperability checks performed
• [x] Data Sovereignty checks performed

General Checks

• [x] Tractus-X Release Guidelines(TRGs) fulfilled https://github.com/eclipse-tractusx/managed-simple-data-exchanger/issues/41

[!NOTE] Note: most criteria for documentation and security are now covered in TRGs

Security Checks

• [x] Thread Modelling Analysis passed

Test Results

• [x] E2E Integration Test passed
• [x] User Journey approved

Helpful Links

• Eclipse Tractus-X openAPI specs on SwaggerHub

[ThomasObermeyer]

@kelaja renewed interoperability based on provided information. Under the assumption the E2E tests with SAP, SupplyOn and Siemens are successful, then the solution is interoperable according to our guidelines.

Interoperability EA approved

[AjayRaturi123]

Security Checks

Thread Modelling Analysis :- https://confluence.catena-x.net/pages/viewpage.action?pageId=62831498 @guenterban Added the document link; please approve.

[AjayRaturi123]

Test Results

1. E2E Integration - https://jira.catena-x.net/browse/TEST-1849 https://jira.catena-x.net/browse/TEST-1983

2. User Journey - No changes since Release R24.03 on User Journey.

[ciprianherciu]

@almadigabor Please confirm that the TRG's were followed for SDE

[ciprianherciu]

@guenterban the Thread Modeling Report can be Found here: https://confluence.catena-x.net/pages/viewpage.action?pageId=62831498 There are no changes from last Release (24.03).

Please helps us approve it

[ciprianherciu]

Product Owner: Ciprian Herciu Dev SPOC: Aditya Gajbhiye Helm Chart Version: 0.1.7 App Version: 2.4.0

[ciprianherciu]

Data Provider (Applications FOSS & COTS incl. Broker)

• [x] A data offer (contract Offer) MAY consist of an access policy and MUST include at least one usage policy.
  • [x] The access policy MUST use CX Standardized credentials.
  • [X] A usage policy MUST refer to at least one Verifiable Credential(Framework Agreement)* (hereinafter referred to as VC). The currently available credentials can be viewed in the CX-0050 standard. The usage policy MUST refer to a confirmed framework agreement which covers the desired scope of data (e.g. traceability, quality,...). It MUST reference the agreement either as a whole or additionally dedicated predefined elements (e.g. purpose - defined in CX-0018 standard) of the framework agreement.
  • [x] In case the data provider is enabled to create contract offers, the data provider MUST be enabled to configure contract offer policies.
• [x] The application MUST use the BPN-L of the data provider when providing data via the DSP connector (e.g. EDC or managed EDC).
• [x] The provider of the connector MUST ensure the provision of data via the DSP protocol adhering to the released version of CX-0018 standard. For example, using the Eclipse Data Space Connector on Tractus X.
  • [x] This provider also MUST ensure that the data provider is uniquely identifiable through its associated BPN-L.
  • [x] This BPN-L must be used by this provider to identify the data.

Data Consumer (Applications FOSS & COTS incl. Broker)

• [x] The provider of the connector MUST ensure the consumption of data via the DSP protocol adhering to the released version of CX-0018 standard. For example, using the Eclipse Data Space Connector on Tractus X. 
  • [x] The application MUST ensure that the consumer of the data is uniquely identifiable through its associated BPN-L.
  • [x] This BPN-L must be used by this application to identify the data.
• [x] The application MUST use the BPN-L of consumer of the data when consuming data via the DSP connector (e.g. EDC or managed EDC).
• [x] A user of an application MUST be enforced to act within the constraints of the framework agreement by appropriate means (legal, technical,...).
• [x] To agree to one or multiple contract offers for a queried data asset, the selection of the appropriate offer MUST be done through the consuming application ensuring to follow company-defined rules and regulations for a user of that application.

[szymonkowalczykzf]

Threat Modeling - Approved All required recommendations are addressed, solutions implemented.

[ciprianherciu]

@vialkoje above we have answered how Data Sov checklist. Please approve the Data Sov, or contact us for more questions Test: https://jira.catena-x.net/browse/TEST-1983 was performed successfully

[cbrugg]

E2E Application Tests finished. INT Tests performed. Data Sov Tests performed by Angelika. @ciprianherciu you still have a Data Sov Testexecution assigned? Interop Tests with Siemens planned this week.

[almadigabor]

Hey @ciprianherciu!

I've prepared the TRG check issue. Before we start we need another committer who joins me to do the checks together. Can you provide me one?

Also Can you fill the description above with the missing information like versions?

Thanks!

[ciprianherciu]

@almadigabor Helm Chart Version: 0.1.7 App Version: 2.4.0

For a second committer as discussed with @RolaH1t at the moment is not a must have. As long as You feel comfortable to make the checks by yourself, it will be accepted in the QG

[cbrugg]

SDE Application INT Tests done / Data Sov Tests done / E2E Tests Done PCF Exchange SDE E2E/INT Tests ongoing / Data Sov Tests done Data Sov was discussed. Only one Testexecution is enough.

[RolaH1t]

QG review 15-May data sov expert approval outstanding user journey approval expected on short notice (PCF & Trace) TRG review pending; committers approached no follow-up mtg required, will monitor via issue

[vialkoje]

As checklist ios answered and tests ran thorugh the expert approval for sovereignty is granted

[almadigabor]

I approve the QG, all issues are resolved. Final versions are:

Helm Chart Version: 0.1.8 App Version: v2.4.0

Thanks @RoKrish14 for the help with the checks!

[ciprianherciu]

The User Journey was approved by Christoph Langdon

[KMA-2019]

@vialkoje , @cbrugg , @ciprianherciu as aligned referencing here notes / feedback from E2E Tests for Data Sovereignty. Based on Angelika Dodels Test Execution, no blocking issues for current Rel 24.05 but some items to be considered for next release(s):

• Note: additional tests (from customer perspective) fully possible
• ContractReference Constraint currently not implemented
• **Declining a specific contract offer based on an unwanted Usage Policy is not possible, i.e. same options will re-appear again upon re-visiting page
• validation of the Schema "profile": "cx-policy:profile2405" not fully checked during test (required to ensure interop with other apps)

[mabige]

@kelaja
All seems be done. Pls. approve.

[Niels1511]

User Journey approved.

[BMWPat]

User Journey for Traceability / Industry Core (Creation of twins and data chain) approved.

[RolaH1t]

Congrats: Quality Gate fully approved with all necessary pre-requisites fulfilled! Thanks for all your efforts, Roland

[almadigabor]

Hey all, a patch has been released, so the new versions approved by me in terms of TRGs are the following:

Helm Chart Version: 0.1.9 App Version: v2.4.1