Add special config for Web Modeler application/client (#4499)

* Add special config for Web Modeler application/client * Remove Keycloak mentioning to keep generic style * update instructions and backport * edit app to application --------- Co-authored-by: Cole Garbo <[email protected]>
camunda · Nov 19, 2024 · 6ee0b9e · 6ee0b9e
1 parent a1a74f8
commit 6ee0b9e
Show file tree

Hide file tree

Showing 4 changed files with 20 additions and 8 deletions.
diff --git a/docs/self-managed/setup/guides/connect-to-an-oidc-provider.md b/docs/self-managed/setup/guides/connect-to-an-oidc-provider.md
@@ -34,11 +34,14 @@ configuration](#component-specific-configuration) to ensure the components are c
 <h3>Steps</h3>
 
 1. In your OIDC provider, create an application for each of the components you want to connect. The expected redirect URI of the component you are configuring an app for can be found in [component-specific configuration](#component-specific-configuration).
-2. Make a note of the following values for each application you create:
+2. For all Components, ensure the appropriate application type is used:
+   - **Operate, Tasklist, Optimize, Identity:** Web applications requiring confidential access/a confidential client
+   - **Web Modeler, Console:** Single-page applications requiring public access/a public client
+3. Make a note of the following values for each application you create:
    - Client ID
    - Client secret
    - Audience
-3. Set the following environment variables for the component you are configuring an app for:
+4. Set the following environment variables for the component you are configuring an app for:
 
 <Tabs groupId="optionsType" defaultValue="env" queryString values={[{label: 'Environment variables', value: 'env' },{label: 'Helm values', value: 'helm' }]} >
 <TabItem value="env">

diff --git a/...naged/platform-deployment/helm-kubernetes/guides/connect-to-an-oidc-provider.md b/...naged/platform-deployment/helm-kubernetes/guides/connect-to-an-oidc-provider.md
@@ -38,11 +38,14 @@ UI is not available for this version.
 <h3>Steps</h3>
 
 1. In your OIDC provider, create an application for each of the components you want to connect. The expected redirect URI of the component you are configuring an app for can be found in [component-specific configuration](#component-specific-configuration).
-2. Make a note of the following values for each application you create:
+2. For all Components, ensure the appropriate application type is used:
+   - **Operate, Tasklist, Optimize, Identity:** Web applications requiring confidential access/a confidential client
+   - **Web Modeler:** A single-page application requiring public access/a public client
+3. Make a note of the following values for each application you create:
    - Client ID
    - Client secret
    - Audience
-3. Set the following environment variables for the component you are configuring an app for:
+4. Set the following environment variables for the component you are configuring an app for:
 
 <Tabs groupId="optionsType" defaultValue="env" queryString values={[{label: 'Environment variables', value: 'env' },{label: 'Helm values', value: 'helm' }]} >
 <TabItem value="env">

diff --git a/...ioned_docs/version-8.5/self-managed/setup/guides/connect-to-an-oidc-provider.md b/...ioned_docs/version-8.5/self-managed/setup/guides/connect-to-an-oidc-provider.md
@@ -34,11 +34,14 @@ configuration](#component-specific-configuration) to ensure the components are c
 <h3>Steps</h3>
 
 1. In your OIDC provider, create an application for each of the components you want to connect. The expected redirect URI of the component you are configuring an app for can be found in [component-specific configuration](#component-specific-configuration).
-2. Make a note of the following values for each application you create:
+2. For all Components, ensure the appropriate application type is used:
+   - **Operate, Tasklist, Optimize, Identity:** Web applications requiring confidential access/a confidential client
+   - **Web Modeler:** A single-page application requiring public access/a public client
+3. Make a note of the following values for each application you create:
    - Client ID
    - Client secret
    - Audience
-3. Set the following environment variables for the component you are configuring an app for:
+4. Set the following environment variables for the component you are configuring an app for:
 
 <Tabs groupId="optionsType" defaultValue="env" queryString values={[{label: 'Environment variables', value: 'env' },{label: 'Helm values', value: 'helm' }]} >
 <TabItem value="env">

diff --git a/...ioned_docs/version-8.6/self-managed/setup/guides/connect-to-an-oidc-provider.md b/...ioned_docs/version-8.6/self-managed/setup/guides/connect-to-an-oidc-provider.md
@@ -34,11 +34,14 @@ configuration](#component-specific-configuration) to ensure the components are c
 <h3>Steps</h3>
 
 1. In your OIDC provider, create an application for each of the components you want to connect. The expected redirect URI of the component you are configuring an app for can be found in [component-specific configuration](#component-specific-configuration).
-2. Make a note of the following values for each application you create:
+2. For all Components, ensure the appropriate application type is used:
+   - **Operate, Tasklist, Optimize, Identity:** Web applications requiring confidential access/a confidential client
+   - **Modeler, Console:** Single-page applications requiring public access/a public client
+3. Make a note of the following values for each application you create:
    - Client ID
    - Client secret
    - Audience
-3. Set the following environment variables for the component you are configuring an app for:
+4. Set the following environment variables for the component you are configuring an app for:
 
 <Tabs groupId="optionsType" defaultValue="env" queryString values={[{label: 'Environment variables', value: 'env' },{label: 'Helm values', value: 'helm' }]} >
 <TabItem value="env">