From 1c39e8d7aeb8f6c90c875e1a1d2448485a01e24e Mon Sep 17 00:00:00 2001 From: Dominik Pinsel Date: Wed, 30 Nov 2022 11:16:03 +0100 Subject: [PATCH 1/2] wip Signed-off-by: Dominik Pinsel --- .../{Version x.x.x.md => Version 0.1.3.md} | 23 +++++++++++++++---- 1 file changed, 19 insertions(+), 4 deletions(-) rename docs/release-notes/{Version x.x.x.md => Version 0.1.3.md} (58%) diff --git a/docs/release-notes/Version x.x.x.md b/docs/release-notes/Version 0.1.3.md similarity index 58% rename from docs/release-notes/Version x.x.x.md rename to docs/release-notes/Version 0.1.3.md index b7ab1060c..e52df5505 100644 --- a/docs/release-notes/Version x.x.x.md +++ b/docs/release-notes/Version 0.1.3.md @@ -1,14 +1,18 @@ -# Release Notes Version 0.1.2 -xx.xx.2022 +# Release Notes Version 0.1.3 + +30.11.2022 # 1. Product EDC ## 1.1 Business Partner Extension **Removed support for Constraint with multiple BPNs** -The possibility to use multiple Business Partner Numbers inside of a single constraint has been removed. It looks like this was only possible due to a missing feature and may lead to unexpected side effects (https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/issues/2026) +The possibility to use multiple Business Partner Numbers inside of a single constraint has been removed. It looks like +this was only possible due to a missing feature and may lead to unexpected side +effects (https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/issues/2026) Hence, this kind of policy is no longer supported! + ```json { "uid": "", @@ -29,7 +33,10 @@ Hence, this kind of policy is no longer supported! }, "rightExpression": { "edctype": "dataspaceconnector:literalexpression", - "value": [ "", "" ] + "value": [ + "", + "" + ] }, "operator": "IN" } @@ -40,3 +47,11 @@ Hence, this kind of policy is no longer supported! ``` The BPN extension will now always decline BPN policies with 'IN' operators, when asked by the EDC to enforce it. + +## 1.2 OAuth2 Extension + +**Add official EDC OAuth2 Extension** +The EDC Oauth2 Extension has now the possibility to add the audience to the claim. So this extension is now again part +of the Control plane and most of the functionality of the CX Oauth2 Extension was removed. + +TODO Write about config change \ No newline at end of file From 4716b5f5c55b9c809384c36e51dcc4255f6de0f6 Mon Sep 17 00:00:00 2001 From: Dominik Pinsel Date: Wed, 30 Nov 2022 11:58:43 +0100 Subject: [PATCH 2/2] update documentation for v0.1.3 Signed-off-by: Dominik Pinsel --- CHANGELOG.md | 10 +++--- docs/migration/Version_0.1.2_0.1.3.md | 20 +++++++++++ docs/release-notes/Version 0.1.3.md | 48 +++++++++++++++++++++++---- 3 files changed, 67 insertions(+), 11 deletions(-) create mode 100644 docs/migration/Version_0.1.2_0.1.3.md diff --git a/CHANGELOG.md b/CHANGELOG.md index 4b9b11b7c..e56013f8e 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -10,17 +10,19 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ### Added - New Postman collection for developers `/docs/development/postman` -- New XSUAA Authenticator Extension ([Readme](/edc-extensions/xsuaa-authenticator/README.md)) +- New EDC Image with HashiCorp Vault and InMemory Storage +- (Experimental) Simplified deployment of the EDC in `/charts/tractusx-connector` -### Updated +### Changed - Set EDC version to `0.0.1-20221006-SNAPSHOT` - Business Partner Number Extension no longer supports the 'IN' constraint operator - HashiCorp Vault Extension now allows sub directories for secrets +- Update package structure/namespace from `net.catenax` to `org.eclipse.tractusx` -### Changed +### Fixed -- Update package structure/namespace from `net.catenax` to `org.eclipse.tractusx` +- S3 Data Transfer ## [0.1.2] - 2022-09-30 diff --git a/docs/migration/Version_0.1.2_0.1.3.md b/docs/migration/Version_0.1.2_0.1.3.md new file mode 100644 index 000000000..55c9c4570 --- /dev/null +++ b/docs/migration/Version_0.1.2_0.1.3.md @@ -0,0 +1,20 @@ +# Migration Version 0.1.2 to 0.1.3 + +This document contains a list of breaking changes that are introduced in version 0.1.3. + +## OAuth2 Extension + +As the images now use the official OAuth2 Extension, the audience settings need to the updated. + +**Add the following settings** +- EDC_OAUTH_PROVIDER_AUDIENCE +- EDC_OAUTH_ENDPOINT_AUDIENCE + +**Remove the following setting** +- EDC_IDS_ENDPOINT_AUDIENCE + +Example +``` +EDC_OAUTH_PROVIDER_AUDIENCE: idsc:IDS_CONNECTORS_ALL +EDC_OAUTH_ENDPOINT_AUDIENCE: http://plato-edc-controlplane:8282/api/v1/ids/data +``` \ No newline at end of file diff --git a/docs/release-notes/Version 0.1.3.md b/docs/release-notes/Version 0.1.3.md index e52df5505..2ee32093f 100644 --- a/docs/release-notes/Version 0.1.3.md +++ b/docs/release-notes/Version 0.1.3.md @@ -2,9 +2,26 @@ 30.11.2022 -# 1. Product EDC +## 0. Summary -## 1.1 Business Partner Extension +1. Container Images + - New Image: HashiCorp Vault & In Memory Store +2. Extensions + - Business Partner Extension + - HashiCorp Vault Extension + - OAuth2 Extension +3. Bug Fixes + - S3 Data Transfer + +# 1. Container Images + +## 1.1 New Image: HashiCorp Vault & In Memory Store + +The EDC now releases a fourth image with a combination of HashiCorp Vault and In Memory Store extensions. + +# 2. Extensions + +## 2.1 Business Partner Extension **Removed support for Constraint with multiple BPNs** The possibility to use multiple Business Partner Numbers inside of a single constraint has been removed. It looks like @@ -48,10 +65,27 @@ Hence, this kind of policy is no longer supported! The BPN extension will now always decline BPN policies with 'IN' operators, when asked by the EDC to enforce it. -## 1.2 OAuth2 Extension +## 2.2 HashiCorp Vault Extension + +It is now possible to arrange HashiCorp Vault secrets in sub-directories. + +For example by storing the DAPS secrets in their own `/daps` directory: + +``` +EDC_OAUTH_PRIVATE_KEY_ALIAS: daps/my-plato-daps-key +EDC_OAUTH_PUBLIC_KEY_ALIAS: daps/my-plato-daps-crt +``` + +## 2.3 OAuth2 Extension + +The EDC Oauth2 Extension has now the possibility to add the audience to the claim. As the official OAuth2 Extension was +added to the control plane again most of the functionality of the CX Oauth2 Extension was removed. + +> **Breaking Change** The official OAuth2 Extension uses different settings then the EDC OAuth Extension. Please +> consolidate the [Migration Documentation](../migration/Version_0.1.2_0.1.3.md). + +# 3. Bug Fixes -**Add official EDC OAuth2 Extension** -The EDC Oauth2 Extension has now the possibility to add the audience to the claim. So this extension is now again part -of the Control plane and most of the functionality of the CX Oauth2 Extension was removed. +## 3.1 S3 Data Transfer -TODO Write about config change \ No newline at end of file +Version 0.1.2 had some issues with the S3 data transfer. This version fixes them. \ No newline at end of file