Skip to content

Commit

Permalink
fix: changing existingSecret.name to comply with schema (#2726)
Browse files Browse the repository at this point in the history
  • Loading branch information
@hamza-m-masood
hamza-m-masood authored Dec 23, 2024
1 parent 7670483 commit c399f09
Show file tree
Hide file tree
Showing 3 changed files with 17 additions and 72 deletions.
10 changes: 5 additions & 5 deletions charts/camunda-platform-alpha/README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -483,7 +483,7 @@ Please see the corresponding [release guide](../../docs/release.md) to find out
| `global.identity.auth.admin` | configuration to configure Connectors authentication specifics on global level, which can be accessed by other components | |
| `global.identity.auth.admin.enabled` | if true, creates the admin client which is used in administration operations if needed. | `false` |
| `global.identity.auth.admin.clientId` | defines the client id. | `admin` |
| `global.identity.auth.admin.existingSecret.name` | can be used to use an own existing secret. If not set a random secret is generated. | `camunda-credentials` |
| `global.identity.auth.admin.existingSecret` | can be used to use an own existing secret. If not set a random secret is generated. Can also reference a k8s secret instead of a string literal by specifying global.identity.auth.admin.existingSecret.name | `{}` |
| `global.identity.auth.admin.existingSecretKey` | defines the key within the existing secret object. | `identity-admin-client-token` |
| `global.identity.auth.identity` | configuration to configure Identity authentication specifics on global level, which can be accessed by other components | |
| `global.identity.auth.identity.clientId` | defines the client id, which is used by Identity in authentication flows. | `camunda-identity` |
Expand All @@ -497,7 +497,7 @@ Please see the corresponding [release guide](../../docs/release.md) to find out
| `global.identity.auth.console.clientId` | defines the client id, which is used by Console in authentication flows. | `console` |
| `global.identity.auth.console.audience` | defines the audience which is used by Console's client API. | `console-api` |
| `global.identity.auth.console.wellKnown` | defines the uri for the well known config which is used by Console (optional). | `https://well-known-uri` |
| `global.identity.auth.console.existingSecret.name` | can be used to use an own existing secret. If not set a random secret is generated. | `camunda-credentials` |
| `global.identity.auth.console.existingSecret` | can be used to use an own existing secret. If not set a random secret is generated. Can also reference a k8s secret instead of a string literal by specifying global.identity.auth.console.existingSecret.name | `{}` |
| `global.identity.auth.console.existingSecretKey` | defines the key within the existing secret object. | `identity-console-client-token` |
| `global.identity.auth.console.redirectUrl` | defines the root URL which is used by Keycloak to access WebModeler. | `http://localhost:8080` |
| `global.identity.auth.webModeler` | configuration to configure WebModeler authentication specifics on global level, which can be accessed by other components | |
Expand All @@ -507,19 +507,19 @@ Please see the corresponding [release guide](../../docs/release.md) to find out
| `global.identity.auth.webModeler.redirectUrl` | defines the root URL which is used by Keycloak to access WebModeler. | `http://localhost:8084` |
| `global.identity.auth.connectors` | configuration to configure Connectors authentication specifics on global level, which can be accessed by other components | |
| `global.identity.auth.connectors.clientId` | defines the client id, which is used by Connectors in authentication flows. | `connectors` |
| `global.identity.auth.connectors.existingSecret.name` | can be used to use an own existing secret. If not set a random secret is generated. | `camunda-credentials` |
| `global.identity.auth.connectors.existingSecret` | can be used to use an own existing secret. If not set a random secret is generated. Can also reference a k8s secret instead of a string literal by specifying global.identity.auth.connectors.existingSecret.name | `{}` |
| `global.identity.auth.connectors.existingSecretKey` | defines the key within the existing secret object. | `identity-connectors-client-token` |
| `global.identity.auth.core` | configuration to configure authentication specifics on global level, which can be accessed by other components | |
| `global.identity.auth.core.audience` | defines the audience, which is used by Core. | `core-api` |
| `global.identity.auth.core.clientId` | defines the client id, which is used by Core in authentication flows. | `core` |
| `global.identity.auth.core.existingSecret.name` | can be used to use an own existing secret. If not set a random secret is generated. | `camunda-credentials` |
| `global.identity.auth.core.existingSecret` | can be used to use an own existing secret. If not set a random secret is generated. Can also reference a k8s secret instead of a string literal by specifying global.identity.auth.core.existingSecret.name | `{}` |
| `global.identity.auth.core.existingSecretKey` | defines the key within the existing secret object. | `identity-core-client-token` |
| `global.identity.auth.core.redirectUrl` | defines the root (or redirect) URL, which is used by Keycloak to access Tasklist. | `http://localhost:8082` |
| `global.identity.auth.core.tokenScope` | defines the token scope, which is used by Core. | `""` |
| `global.identity.auth.optimize` | configuration to configure Optimize authentication specifics on global level, which can be accessed by other components | |
| `global.identity.auth.optimize.audience` | defines the audience, which is used by Optimize. | `optimize-api` |
| `global.identity.auth.optimize.clientId` | defines the client id, which is used by Optimize in authentication flows. | `optimize` |
| `global.identity.auth.optimize.existingSecret.name` | can be used to use an own existing secret. If not set a random secret is generated. | `camunda-credentials` |
| `global.identity.auth.optimize.existingSecret` | can be used to use an own existing secret. If not set a random secret is generated. Can also reference a k8s secret instead of a string literal by specifying global.identity.auth.optimize.existingSecret.name | `{}` |
| `global.identity.auth.optimize.existingSecretKey` | defines the key within the existing secret object. | `identity-optimize-client-token` |
| `global.identity.auth.optimize.redirectUrl` | defines the root (or redirect) URL, which is used by Keycloak to access Optimize. | `http://localhost:8083` |

Expand Down
Loading

0 comments on commit c399f09

Please sign in to comment.