Release version 0.7.0

.github/release.yaml

@@ -21,15 +21,23 @@
 ---
 changelog:
   exclude:
+    labels:
+      - dependencies
     authors:
-      - dependabot[bot]
+      - 'dependabot[bot]'
   categories:
+    - title: Breaking changes
+      labels:
+        - breaking-change
     - title: Bugfixes
       labels:
         - bug
     - title: New Features & Improvements
       labels:
-        - "*"
+        - enhancement
     - title: Documentation
       labels:
         - documentation
+    - title: Other Changes
+      labels:
+        - "*"

.github/workflows/verify.yaml

@@ -125,14 +125,14 @@ jobs:
 
       - name: Run E2E tests (${{ matrix.variant.dir }})
         run: |
-          ./gradlew compileJava compileTestJava
-          ./gradlew -p ${{ matrix.variant.dir }} test -DincludeTags="EndToEndTest"
+          ./gradlew compileJava compileTestJava --refresh-dependencies
+          ./gradlew -p ${{ matrix.variant.dir }} test -DincludeTags="EndToEndTest" 
 
   postgres-tests:
     runs-on: ubuntu-latest
     services:
       postgres:
-        image: postgres:14.2
+        image: postgres:16.1
         ports:
           - 5432:5432
         env:
@@ -143,7 +143,7 @@ jobs:
       - uses: ./.github/actions/setup-java
 
       - name: Run Postgresql E2E tests
-        run: ./gradlew test -DincludeTags="PostgresqlIntegrationTest"
+        run: ./gradlew test -DincludeTags="PostgresqlIntegrationTest" --refresh-dependencies
 
   dataplane-tests:
     runs-on: ubuntu-latest

build.gradle.kts

@@ -28,7 +28,7 @@ plugins {
     `jacoco-report-aggregation`
     id("com.github.johnrengelman.shadow") version "8.1.1"
     id("com.bmuschko.docker-remote-api") version "9.4.0"
-    id("io.github.gradle-nexus.publish-plugin") version "1.3.0"
+    id("io.github.gradle-nexus.publish-plugin") version "2.0.0"
 }
 
 val txScmConnection: String by project

charts/tractusx-connector-azure-vault/Chart.yaml

@@ -41,12 +41,12 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 0.7.0-rc1
+version: 0.7.0
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
 # It is recommended to use it with quotes.
-appVersion: "0.7.0-rc1"
+appVersion: "0.7.0"
 home: https://github.com/eclipse-tractusx/tractusx-edc/tree/main/charts/tractusx-connector
 sources:
   - https://github.com/eclipse-tractusx/tractusx-edc/tree/main/charts/tractusx-connector

charts/tractusx-connector-azure-vault/README.md

@@ -1,6 +1,6 @@
 # tractusx-connector-azure-vault
 
-![Version: 0.7.0-rc1](https://img.shields.io/badge/Version-0.7.0--rc1-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 0.7.0-rc1](https://img.shields.io/badge/AppVersion-0.7.0--rc1-informational?style=flat-square)
+![Version: 0.7.0](https://img.shields.io/badge/Version-0.7.0-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 0.7.0](https://img.shields.io/badge/AppVersion-0.7.0-informational?style=flat-square)
 
 A Helm chart for Tractus-X Eclipse Data Space Connector. The connector deployment consists of two runtime consists of a
 Control Plane and a Data Plane. Note that _no_ external dependencies such as a PostgreSQL database and Azure KeyVault are included.
@@ -9,33 +9,32 @@ This chart is intended for use with an _existing_ PostgreSQL database and an _ex
 
 **Homepage:** <https://github.com/eclipse-tractusx/tractusx-edc/tree/main/charts/tractusx-connector>
 
-## Setting up SSI
+## Setting up IATP
 
 ### Preconditions
 
-- the [Managed Identity Walled (MIW)](https://github.com/eclipse-tractusx/managed-identity-wallet) must be running and reachable via network
-- the necessary set of VerifiableCredentials for this participant must be pushed to MIW. This is typically done by the
+- You'll need an account with DIM, the wallet for VerifiableCredentials
+- the necessary set of VerifiableCredentials for this participant must already be issued to your DIM tenant. This is typically done by the
   Portal during participant onboarding
-- KeyCloak must be running and reachable via network
-- an account with KeyCloak must be created for this BPN and the connector must be able to obtain access tokens
 - the client ID and client secret corresponding to that account must be known
 
 ### Preparatory work
 
-- store your KeyCloak client secret in the Azure KeyVault. The exact procedure is as follows:
- ```bash
- az keyvault secret set --vault-name <YOUR_VAULT_NAME> --name client-secret --value "$YOUR_CLIENT_SECRET"
- ```
- By default, Tractus-X EDC expects to find the secret under `client-secret`.
+- store client secret in the HashiCorp vault using an alias. The exact procedure will depend on your deployment of HashiCorp Vault and
+  is out of scope of this document. But by default, Tractus-X EDC expects to find the secret under `secret/client-secret`. The alias must be configured
+  using the `iatp.sts.oauth.client.secret_alias` Helm value.
 
 ### Configure the chart
 
 Be sure to provide the following configuration entries to your Tractus-X EDC Helm chart:
-- `controlplane.ssi.miw.url`: the URL
-- `controlplane.ssi.miw.authorityId`: the BPN of the issuer authority
-- `controlplane.ssi.oauth.tokenurl`: the URL (of KeyCloak), where access tokens can be obtained
-- `controlplane.ssi.oauth.client.id`: client ID for KeyCloak
-- `controlplane.ssi.oauth.client.secretAlias`: the alias under which the client secret is stored in the vault. Defaults to `client-secret`.
+- `iatp.sts.oauth.token_url`: the token endpoint of DIM
+- `iatp.sts.oauth.client.id`: the client ID of your tenant in DIM
+- `iatp.sts.oauth.client.secret_alias`: alias under which you saved your DIM client secret in the vault
+- `iatp.sts.dim.url`: the base URL for DIM
+
+In addition, in order to map BPNs to DIDs, a new service is required, called the BPN-DID Resolution Service, which
+must be configured:
+- `controlplane.bdrs.server.url`: base URL of the BPN-DID Resolution Service ("BDRS")
 
 ### Launching the application
 
@@ -45,7 +44,7 @@ Combined, run this shell command to start the in-memory Tractus-X EDC runtime:
 
 ```shell
 helm repo add tractusx-edc https://eclipse-tractusx.github.io/charts/dev
-helm install my-release tractusx-edc/tractusx-connector-azure-vault --version 0.7.0-rc1 \
+helm install my-release tractusx-edc/tractusx-connector-azure-vault --version 0.7.0 \
      -f <path-to>/tractusx-connector-azure-vault-test.yaml \
      --set vault.azure.name=$AZURE_VAULT_NAME \
      --set vault.azure.client=$AZURE_CLIENT_ID \

charts/tractusx-connector-azure-vault/README.md.gotmpl

@@ -8,35 +8,33 @@
 
 {{ template "chart.homepageLine" . }}
 
-## Setting up SSI
+## Setting up IATP
 
 ### Preconditions
 
-- the [Managed Identity Walled (MIW)](https://github.com/eclipse-tractusx/managed-identity-wallet) must be running and reachable via network
-- the necessary set of VerifiableCredentials for this participant must be pushed to MIW. This is typically done by the
+- You'll need an account with DIM, the wallet for VerifiableCredentials
+- the necessary set of VerifiableCredentials for this participant must already be issued to your DIM tenant. This is typically done by the
   Portal during participant onboarding
-- KeyCloak must be running and reachable via network
-- an account with KeyCloak must be created for this BPN and the connector must be able to obtain access tokens
 - the client ID and client secret corresponding to that account must be known
 
 ### Preparatory work
 
-- store your KeyCloak client secret in the Azure KeyVault. The exact procedure is as follows:
- ```bash
- az keyvault secret set --vault-name <YOUR_VAULT_NAME> --name client-secret --value "$YOUR_CLIENT_SECRET"
- ```
- By default, Tractus-X EDC expects to find the secret under `client-secret`.
+- store client secret in the HashiCorp vault using an alias. The exact procedure will depend on your deployment of HashiCorp Vault and
+  is out of scope of this document. But by default, Tractus-X EDC expects to find the secret under `secret/client-secret`. The alias must be configured
+  using the `iatp.sts.oauth.client.secret_alias` Helm value.
 
 
 ### Configure the chart
 
 Be sure to provide the following configuration entries to your Tractus-X EDC Helm chart:
-- `controlplane.ssi.miw.url`: the URL
-- `controlplane.ssi.miw.authorityId`: the BPN of the issuer authority
-- `controlplane.ssi.oauth.tokenurl`: the URL (of KeyCloak), where access tokens can be obtained
-- `controlplane.ssi.oauth.client.id`: client ID for KeyCloak
-- `controlplane.ssi.oauth.client.secretAlias`: the alias under which the client secret is stored in the vault. Defaults to `client-secret`.
+- `iatp.sts.oauth.token_url`: the token endpoint of DIM
+- `iatp.sts.oauth.client.id`: the client ID of your tenant in DIM
+- `iatp.sts.oauth.client.secret_alias`: alias under which you saved your DIM client secret in the vault
+- `iatp.sts.dim.url`: the base URL for DIM
 
+In addition, in order to map BPNs to DIDs, a new service is required, called the BPN-DID Resolution Service, which
+must be configured:
+- `controlplane.bdrs.server.url`: base URL of the BPN-DID Resolution Service ("BDRS")
 
 ### Launching the application
 
@@ -54,7 +52,6 @@ helm install my-release tractusx-edc/tractusx-connector-azure-vault --version {{
      --set vault.azure.tenant=$AZURE_TENANT_ID
 ```
 
-
 {{ template "chart.maintainersSection" . }}
 
 {{ template "chart.sourcesSection" . }}

charts/tractusx-connector-memory/Chart.yaml

@@ -35,12 +35,12 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 0.7.0-rc1
+version: 0.7.0
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
 # It is recommended to use it with quotes.
-appVersion: "0.7.0-rc1"
+appVersion: "0.7.0"
 home: https://github.com/eclipse-tractusx/tractusx-edc/tree/main/charts/tractusx-connector-memory
 sources:
   - https://github.com/eclipse-tractusx/tractusx-edc/tree/main/charts/tractusx-connector-memory

charts/tractusx-connector-memory/README.md

@@ -1,35 +1,37 @@
 # tractusx-connector-memory
 
-![Version: 0.7.0-rc1](https://img.shields.io/badge/Version-0.7.0--rc1-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 0.7.0-rc1](https://img.shields.io/badge/AppVersion-0.7.0--rc1-informational?style=flat-square)
+![Version: 0.7.0](https://img.shields.io/badge/Version-0.7.0-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 0.7.0](https://img.shields.io/badge/AppVersion-0.7.0-informational?style=flat-square)
 
 A Helm chart for Tractus-X Eclipse Data Space Connector based on memory. Please only use this for development or testing purposes, never in production workloads!
 
 **Homepage:** <https://github.com/eclipse-tractusx/tractusx-edc/tree/main/charts/tractusx-connector-memory>
 
-## Setting up SSI
+## Setting up IATP
 
 ### Preconditions
 
-- the [Managed Identity Walled (MIW)](https://github.com/eclipse-tractusx/managed-identity-wallet) must be running and reachable via network
-- the necessary set of VerifiableCredentials for this participant must be pushed to MIW. This is typically done by the
+- You'll need an account with DIM, the wallet for VerifiableCredentials
+- the necessary set of VerifiableCredentials for this participant must already be issued to your DIM tenant. This is typically done by the
   Portal during participant onboarding
-- KeyCloak must be running and reachable via network
-- an account with KeyCloak must be created for this BPN and the connector must be able to obtain access tokens
 - the client ID and client secret corresponding to that account must be known
 
 ### Preparatory work
 
-- store your KeyCloak client secret in the HashiCorp vault. The exact procedure will depend on your deployment of HashiCorp Vault and
-  is out of scope of this document. But by default, Tractus-X EDC expects to find the secret under `secret/client-secret`.
+- store client secret in the HashiCorp vault using an alias. The exact procedure will depend on your deployment of HashiCorp Vault and
+  is out of scope of this document. But by default, Tractus-X EDC expects to find the secret under `secret/client-secret`. The alias must be configured
+  using the `iatp.sts.oauth.client.secret_alias` Helm value.
 
 ### Configure the chart
 
 Be sure to provide the following configuration entries to your Tractus-X EDC Helm chart:
-- `runtime.ssi.miw.url`: the URL
-- `runtime.ssi.miw.authorityId`: the BPN of the issuer authority
-- `runtime.ssi.oauth.tokenurl`: the URL (of KeyCloak), where access tokens can be obtained
-- `runtime.ssi.oauth.client.id`: client ID for KeyCloak
-- `runtime.ssi.oauth.client.secretAlias`: the alias under which the client secret is stored in the vault. Defaults to `client-secret`.
+- `iatp.sts.oauth.token_url`: the token endpoint of DIM
+- `iatp.sts.oauth.client.id`: the client ID of your tenant in DIM
+- `iatp.sts.oauth.client.secret_alias`: alias under which you saved your DIM client secret in the vault
+- `iatp.sts.dim.url`: the base URL for DIM
+
+In addition, in order to map BPNs to DIDs, a new service is required, called the BPN-DID Resolution Service, which
+must be configured:
+- `controlplane.bdrs.server.url`: base URL of the BPN-DID Resolution Service ("BDRS")
 
 ### Launching the application
 
@@ -39,7 +41,7 @@ Combined, run this shell command to start the in-memory Tractus-X EDC runtime:
 
 ```shell
 helm repo add tractusx-edc https://eclipse-tractusx.github.io/charts/dev
-helm install my-release tractusx-edc/tractusx-connector-memory --version 0.7.0-rc1 \
+helm install my-release tractusx-edc/tractusx-connector-memory --version 0.7.0 \
      -f <path-to>/tractusx-connector-memory-test.yaml \
      --set vault.secrets="client-secret:$YOUR_CLIENT_SECRET"
 ```

charts/tractusx-connector-memory/README.md.gotmpl

@@ -8,32 +8,33 @@
 
 {{ template "chart.homepageLine" . }}
 
-## Setting up SSI
+## Setting up IATP
 
 ### Preconditions
 
-- the [Managed Identity Walled (MIW)](https://github.com/eclipse-tractusx/managed-identity-wallet) must be running and reachable via network
-- the necessary set of VerifiableCredentials for this participant must be pushed to MIW. This is typically done by the
+- You'll need an account with DIM, the wallet for VerifiableCredentials
+- the necessary set of VerifiableCredentials for this participant must already be issued to your DIM tenant. This is typically done by the
   Portal during participant onboarding
-- KeyCloak must be running and reachable via network
-- an account with KeyCloak must be created for this BPN and the connector must be able to obtain access tokens
 - the client ID and client secret corresponding to that account must be known
 
 ### Preparatory work
 
-- store your KeyCloak client secret in the HashiCorp vault. The exact procedure will depend on your deployment of HashiCorp Vault and
-  is out of scope of this document. But by default, Tractus-X EDC expects to find the secret under `secret/client-secret`.
+- store client secret in the HashiCorp vault using an alias. The exact procedure will depend on your deployment of HashiCorp Vault and
+  is out of scope of this document. But by default, Tractus-X EDC expects to find the secret under `secret/client-secret`. The alias must be configured
+  using the `iatp.sts.oauth.client.secret_alias` Helm value.
 
 
 ### Configure the chart
 
 Be sure to provide the following configuration entries to your Tractus-X EDC Helm chart:
-- `runtime.ssi.miw.url`: the URL
-- `runtime.ssi.miw.authorityId`: the BPN of the issuer authority
-- `runtime.ssi.oauth.tokenurl`: the URL (of KeyCloak), where access tokens can be obtained
-- `runtime.ssi.oauth.client.id`: client ID for KeyCloak
-- `runtime.ssi.oauth.client.secretAlias`: the alias under which the client secret is stored in the vault. Defaults to `client-secret`.
-
+- `iatp.sts.oauth.token_url`: the token endpoint of DIM
+- `iatp.sts.oauth.client.id`: the client ID of your tenant in DIM
+- `iatp.sts.oauth.client.secret_alias`: alias under which you saved your DIM client secret in the vault
+- `iatp.sts.dim.url`: the base URL for DIM
+
+In addition, in order to map BPNs to DIDs, a new service is required, called the BPN-DID Resolution Service, which
+must be configured:
+- `controlplane.bdrs.server.url`: base URL of the BPN-DID Resolution Service ("BDRS")
 
 ### Launching the application
 

charts/tractusx-connector/Chart.yaml

@@ -41,12 +41,12 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 0.7.0-rc1
+version: 0.7.0
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
 # It is recommended to use it with quotes.
-appVersion: "0.7.0-rc1"
+appVersion: "0.7.0"
 home: https://github.com/eclipse-tractusx/tractusx-edc/tree/main/charts/tractusx-connector
 sources:
   - https://github.com/eclipse-tractusx/tractusx-edc/tree/main/charts/tractusx-connector