diff --git a/docs/self-managed/identity/user-guide/configuration/connect-to-an-existing-keycloak.md b/docs/self-managed/identity/user-guide/configuration/connect-to-an-existing-keycloak.md index 1173b3be59e..835be739ecc 100644 --- a/docs/self-managed/identity/user-guide/configuration/connect-to-an-existing-keycloak.md +++ b/docs/self-managed/identity/user-guide/configuration/connect-to-an-existing-keycloak.md @@ -18,6 +18,12 @@ Clients in Camunda 8 SaaS and applications in Camunda 8 Self-Managed provide a s ## Steps +:::caution Keycloak URLs +As of the 8.5.3 release, Identity uses the Keycloak frontend URL instead of the backend URL. This change may affect you if you have blocked the Keycloak frontend URL from other services (including Camunda applications), and can potentially impact Identity's functionality. + +To avoid connectivity issues, ensure your Keycloak frontend URL is accessible by adjusting your network, firewall, or security settings as needed. This adjustment is crucial to maintain the integration with Keycloak and ensure compatibility. +::: + To connect Identity to an existing Keycloak instance, take the following steps: 1. Log in to your Keycloak Admin Console. diff --git a/docs/self-managed/operational-guides/update-guide/840-to-850.md b/docs/self-managed/operational-guides/update-guide/840-to-850.md index 864a994ddd5..b94830b187a 100644 --- a/docs/self-managed/operational-guides/update-guide/840-to-850.md +++ b/docs/self-managed/operational-guides/update-guide/840-to-850.md @@ -72,3 +72,9 @@ since the Zeebe user tasks are only experimental in `8.4`. If you need the data on migrated user task instances, you can reactivate them using [Process Instance Modification](/components/concepts/process-instance-modification.md). This results in a `UserTask:CANCELED` event for the existing user task and a new `UserTask:CREATED` event with the `candidateUsersList` and `candidateGroupsList` filled based on what is configured in the process model. ::: + +## Identity + +Identity now uses the Keycloak frontend URL instead of the backend URL. This change may affect you if you have blocked the Keycloak frontend URL from other services (including Camunda applications), and can potentially impact Identity's functionality. + +To avoid connectivity issues, ensure your Keycloak frontend URL is accessible by adjusting your network, firewall, or security settings as needed. This adjustment is crucial to maintain the integration with Keycloak and ensure compatibility. diff --git a/versioned_docs/version-8.5/reference/announcements.md b/versioned_docs/version-8.5/reference/announcements.md index e4f95e7dca6..01a02b3ef83 100644 --- a/versioned_docs/version-8.5/reference/announcements.md +++ b/versioned_docs/version-8.5/reference/announcements.md @@ -103,6 +103,12 @@ Timestamps which were previously serialized as `ISO8061` strings are now seriali Until a fix is delivered in 8.5.1, workarounds include not deserializing timestamp values from affected APIs, or deserializing them as integers. +### Identity Keycloak URL changes + +Identity now uses the Keycloak frontend URL instead of the backend URL. This change may affect you if you have blocked the Keycloak frontend URL from other services (including Camunda applications), and can potentially impact Identity's functionality. + +To avoid connectivity issues, ensure your Keycloak frontend URL is accessible by adjusting your network, firewall, or security settings as needed. This adjustment is crucial to maintain the integration with Keycloak and ensure compatibility. + ## Camunda 8.4 Release date: 9th of January 2024 diff --git a/versioned_docs/version-8.5/self-managed/identity/user-guide/configuration/connect-to-an-existing-keycloak.md b/versioned_docs/version-8.5/self-managed/identity/user-guide/configuration/connect-to-an-existing-keycloak.md index 1173b3be59e..835be739ecc 100644 --- a/versioned_docs/version-8.5/self-managed/identity/user-guide/configuration/connect-to-an-existing-keycloak.md +++ b/versioned_docs/version-8.5/self-managed/identity/user-guide/configuration/connect-to-an-existing-keycloak.md @@ -18,6 +18,12 @@ Clients in Camunda 8 SaaS and applications in Camunda 8 Self-Managed provide a s ## Steps +:::caution Keycloak URLs +As of the 8.5.3 release, Identity uses the Keycloak frontend URL instead of the backend URL. This change may affect you if you have blocked the Keycloak frontend URL from other services (including Camunda applications), and can potentially impact Identity's functionality. + +To avoid connectivity issues, ensure your Keycloak frontend URL is accessible by adjusting your network, firewall, or security settings as needed. This adjustment is crucial to maintain the integration with Keycloak and ensure compatibility. +::: + To connect Identity to an existing Keycloak instance, take the following steps: 1. Log in to your Keycloak Admin Console. diff --git a/versioned_docs/version-8.5/self-managed/operational-guides/update-guide/840-to-850.md b/versioned_docs/version-8.5/self-managed/operational-guides/update-guide/840-to-850.md index 864a994ddd5..b94830b187a 100644 --- a/versioned_docs/version-8.5/self-managed/operational-guides/update-guide/840-to-850.md +++ b/versioned_docs/version-8.5/self-managed/operational-guides/update-guide/840-to-850.md @@ -72,3 +72,9 @@ since the Zeebe user tasks are only experimental in `8.4`. If you need the data on migrated user task instances, you can reactivate them using [Process Instance Modification](/components/concepts/process-instance-modification.md). This results in a `UserTask:CANCELED` event for the existing user task and a new `UserTask:CREATED` event with the `candidateUsersList` and `candidateGroupsList` filled based on what is configured in the process model. ::: + +## Identity + +Identity now uses the Keycloak frontend URL instead of the backend URL. This change may affect you if you have blocked the Keycloak frontend URL from other services (including Camunda applications), and can potentially impact Identity's functionality. + +To avoid connectivity issues, ensure your Keycloak frontend URL is accessible by adjusting your network, firewall, or security settings as needed. This adjustment is crucial to maintain the integration with Keycloak and ensure compatibility.