You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- store your KeyCloak client secret in the Azure KeyVault. The exact procedure is as follows:
26
+
```bash
27
+
az keyvault secret set --vault-name <YOUR_VAULT_NAME> --name client-secret --value "$YOUR_CLIENT_SECRET"
28
+
```
29
+
By default, Tractus-X EDC expects to find the secret under `client-secret`.
28
30
29
-
The following requirements must be met before launching the application:
31
+
### Configure the chart
30
32
31
-
- Write access to an Azure KeyVault instance is required to run this chart
32
-
- Secrets are seeded in advance
33
-
- The vault's client id, client secret, tenant id and vault name (not the url!) are known
33
+
Be sure to provide the following configuration entries to your Tractus-X EDC Helm chart:
34
+
-`controlplane.ssi.miw.url`: the URL
35
+
-`controlplane.ssi.miw.authorityId`: the BPN of the issuer authority
36
+
-`controlplane.ssi.oauth.tokenurl`: the URL (of KeyCloak), where access tokens can be obtained
37
+
-`controlplane.ssi.oauth.client.id`: client ID for KeyCloak
38
+
-`controlplane.ssi.oauth.client.secretAlias`: the alias under which the client secret is stored in the vault. Defaults to `client-secret`.
34
39
35
-
Please also consider using [this example configuration](https://github.com/eclipse-tractusx/tractusx-edc/blob/main/edc-tests/deployment/src/main/resources/helm/tractusx-connector-azure-vault-test.yaml)
36
-
to launch the application.
40
+
### Launching the application
41
+
42
+
As an easy starting point, please consider using [this example configuration](https://github.com/eclipse-tractusx/tractusx-edc/blob/main/edc-tests/deployment/src/main/resources/helm/tractusx-connector-test.yaml)
43
+
to launch the application. The configuration values mentioned above (`controlplane.ssi.*`) will have to be adapted manually.
37
44
Combined, run this shell command to start the in-memory Tractus-X EDC runtime:
| controlplane.service.type | string |`"ClusterIP"`|[Service type](https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types) to expose the running application on a set of Pods as a network service. |
- store your KeyCloak client secret in the Azure KeyVault. The exact procedure is as follows:
25
+
```bash
26
+
az keyvault secret set --vault-name <YOUR_VAULT_NAME> --name client-secret --value "$YOUR_CLIENT_SECRET"
27
+
```
28
+
By default, Tractus-X EDC expects to find the secret under `client-secret`.
25
29
26
-
## Launching the application
27
30
28
-
The following requirements must be met before launching the application:
31
+
### Configure the chart
29
32
30
-
- Write access to an Azure KeyVault instance is required to run this chart
31
-
- Secrets are seeded in advance
32
-
- The vault's client id, client secret, tenant id and vault name (not the url!) are known
33
+
Be sure to provide the following configuration entries to your Tractus-X EDC Helm chart:
34
+
- `controlplane.ssi.miw.url`: the URL
35
+
- `controlplane.ssi.miw.authorityId`: the BPN of the issuer authority
36
+
- `controlplane.ssi.oauth.tokenurl`: the URL (of KeyCloak), where access tokens can be obtained
37
+
- `controlplane.ssi.oauth.client.id`: client ID for KeyCloak
38
+
- `controlplane.ssi.oauth.client.secretAlias`: the alias under which the client secret is stored in the vault. Defaults to `client-secret`.
33
39
34
-
Please also consider using [this example configuration](https://github.com/eclipse-tractusx/tractusx-edc/blob/main/edc-tests/deployment/src/main/resources/helm/tractusx-connector-azure-vault-test.yaml)
35
-
to launch the application.
40
+
41
+
### Launching the application
42
+
43
+
As an easy starting point, please consider using [this example configuration](https://github.com/eclipse-tractusx/tractusx-edc/blob/main/edc-tests/deployment/src/main/resources/helm/tractusx-connector-test.yaml)
44
+
to launch the application. The configuration values mentioned above (`controlplane.ssi.*`) will have to be adapted manually.
36
45
Combined, run this shell command to start the in-memory Tractus-X EDC runtime:
Copy file name to clipboardExpand all lines: charts/tractusx-connector-azure-vault/values.yaml
-2
Original file line number
Diff line number
Diff line change
@@ -139,8 +139,6 @@ controlplane:
139
139
client:
140
140
id: ""
141
141
secretAlias: "client-secret"
142
-
endpoint:
143
-
audience: "http://this.audience"
144
142
service:
145
143
# -- [Service type](https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types) to expose the running application on a set of Pods as a network service.
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!
- store your KeyCloak client secret in the HashiCorp vault. The exact procedure will depend on your deployment of HashiCorp Vault and
23
+
is out of scope of this document. But by default, Tractus-X EDC expects to find the secret under `secret/client-secret`.
22
24
23
-
##Launching the application
25
+
### Configure the chart
24
26
25
-
The in-memory vault can be seeded directly with secrets that are passed in `<key>:<value>;<key2>:<value2>;...` format.
26
-
This config value can be passed to the runtime using the `vault.secrets` parameter. In addition, the runtime requires a
27
-
couple of configuration parameters, all of which can be found in the section below. Please also consider using
28
-
[this example configuration](https://github.com/eclipse-tractusx/tractusx-edc/blob/main/edc-tests/deployment/src/main/resources/helm/tractusx-connector-memory-test.yaml)
29
-
to launch the application.
27
+
Be sure to provide the following configuration entries to your Tractus-X EDC Helm chart:
28
+
-`runtime.ssi.miw.url`: the URL
29
+
-`runtime.ssi.miw.authorityId`: the BPN of the issuer authority
30
+
-`runtime.ssi.oauth.tokenurl`: the URL (of KeyCloak), where access tokens can be obtained
31
+
-`runtime.ssi.oauth.client.id`: client ID for KeyCloak
32
+
-`runtime.ssi.oauth.client.secretAlias`: the alias under which the client secret is stored in the vault. Defaults to `client-secret`.
30
33
34
+
### Launching the application
35
+
36
+
As an easy starting point, please consider using [this example configuration](https://github.com/eclipse-tractusx/tractusx-edc/blob/main/edc-tests/deployment/src/main/resources/helm/tractusx-connector-test.yaml)
37
+
to launch the application. The configuration values mentioned above (`controlplane.ssi.*`) will have to be adapted manually.
31
38
Combined, run this shell command to start the in-memory Tractus-X EDC runtime:
@@ -157,7 +162,6 @@ Note that `DAPS_CERT` contains the x509 certificate, `DAPS_KEY` contains the pri
157
162
| runtime.securityContext.runAsUser | int |`10001`| The container's process will run with the specified uid |
158
163
| runtime.service.annotations | object |`{}`||
159
164
| runtime.service.type | string |`"ClusterIP"`|[Service type](https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types) to expose the running application on a set of Pods as a network service. |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4&size=40){kind=avatar}
0 commit comments