docs(identity): Add note regarding single sign out limitation (#3500)

* docs(identity): Add note regarding single sign out limitation * docs(identity): backport to 8.4 docs regarding single sign out limitation
camunda · Apr 3, 2024 · c6d8714 · c6d8714
1 parent 36f6b3f
commit c6d8714
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 0 deletions.
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
@@ -197,6 +197,9 @@ global:
 
 ### Additional considerations
 
+Due to technical limitations regarding [third party content](https://openid.net/specs/openid-connect-frontchannel-1_0.html#ThirdPartyContent),
+front channel single sign out is not supported. This means that when a user logs out of one component, they will not be logged out of the other components.
+
 For authentication, the Camunda components use the scopes `email`, `openid`, `offline_access`, `profile`,
 and `<CLIENT_UUID>/.default`. To ensure your users are able to successfully authenticate with Entra ID, you must
 ensure that either there is

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
@@ -184,6 +184,9 @@ global:
 
 ### Additional considerations
 
+Due to technical limitations regarding [third party content](https://openid.net/specs/openid-connect-frontchannel-1_0.html#ThirdPartyContent),
+front channel single sign out is not supported. This means that when a user logs out of one component, they will not be logged out of the other components.
+
 For authentication, the Camunda components use the scopes `email`, `openid`, `offline_access`, `profile`,
 and `<CLIENT_UUID>/.default`. To ensure your users are able to successfully authenticate with Entra ID, you must
 ensure that either there is