Skip to content

Commit

Permalink
Fix Keycloak link
Browse files Browse the repository at this point in the history
  • Loading branch information
@mesellings
mesellings committed Jan 21, 2025
1 parent 4142a40 commit 6a5b1fe
Show file tree
Hide file tree
Showing 4 changed files with 20 additions and 20 deletions.
10 changes: 5 additions & 5 deletions docs/self-managed/identity/troubleshooting/troubleshoot-identity.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -74,19 +74,19 @@ When the Keycloak service is ready for connections, start (or restart) the Ident
### Solution 2: Identity making requests from an external IP address

By default, Keycloak requires TLS on requests that originate from what it considers to be an external source. The Keycloak
documentation for [setting up SSL](https://www.keycloak.org/docs/latest/server_admin/#_ssl_modes) maintains
a list of what they consider to be an external IP address under the `external requests` section.
documentation for [configuring SSL for a realm](https://www.keycloak.org/docs/latest/server_admin/#_ssl_modes) maintains
a list of what Keycloak considers to be an external IP address in the `external requests` section.

The solution to this issue will depend largely on your environment. However, as a starting point we would suggest you consider
these options:

1. Configure the communication between the services (for example in a cluster) to use IP ranges that fall within the
ranges that Keycloak expects.
2. If configuring the IP ranges is not an option, it is possible to disable the SSL requirement in Keycloak itself by completing the following steps:
1. In the `master` realm, set `Require SSL` to `none` by following the steps in [SSL modes](https://www.keycloak.org/docs/23.0.1/server_admin/#_ssl_modes).
1. In the `master` realm, set `Require SSL` to `none` by following the steps in [configuring SSL for a realm](https://www.keycloak.org/docs/latest/server_admin/#_ssl_modes).
2. Restart the Identity service.
3. In the `camunda-platform` realm, set `Require SSL` to `none` by following the steps in [SSL modes](https://www.keycloak.org/docs/23.0.1/server_admin/#_ssl_modes).
4. Restart the Identity service again. Identity should now start successfully
3. In the `camunda-platform` realm, set `Require SSL` to `none` by following the steps in [configuring SSL for a realm](https://www.keycloak.org/docs/latest/server_admin/#_ssl_modes).
4. Restart the Identity service again. Identity should now start successfully.

:::warning
We would only recommend that requirements for SSL are disabled in a development environment.
Expand Down
10 changes: 5 additions & 5 deletions ...docs/version-8.4/self-managed/identity/troubleshooting/troubleshoot-identity.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -74,19 +74,19 @@ When the Keycloak service is ready for connections, start (or restart) the Ident
### Solution 2: Identity making requests from an external IP address

By default, Keycloak requires TLS on requests that originate from what it considers to be an external source. The Keycloak
documentation for [setting up SSL](https://www.keycloak.org/docs/latest/server_admin/#_ssl_modes) maintains
a list of what they consider to be an external IP address under the `external requests` section.
documentation for [configuring SSL for a realm](https://www.keycloak.org/docs/latest/server_admin/#_ssl_modes) maintains
a list of what Keycloak considers to be an external IP address in the `external requests` section.

The solution to this issue will depend largely on your environment. However, as a starting point we would suggest you consider
these options:

1. Configure the communication between the services (for example in a cluster) to use IP ranges that fall within the
ranges that Keycloak expects.
2. If configuring the IP ranges is not an option, it is possible to disable the SSL requirement in Keycloak itself by completing the following steps:
1. In the `master` realm, set `Require SSL` to `none` by following the steps in [SSL modes](https://www.keycloak.org/docs/22.0.1/server_admin/#_ssl_modes).
1. In the `master` realm, set `Require SSL` to `none` by following the steps in [configuring SSL for a realm](https://www.keycloak.org/docs/latest/server_admin/#_ssl_modes).
2. Restart the Identity service.
3. In the `camunda-platform` realm, set `Require SSL` to `none` by following the steps in [SSL modes](https://www.keycloak.org/docs/22.0.1/server_admin/#_ssl_modes).
4. Restart the Identity service again. Identity should now start successfully
3. In the `camunda-platform` realm, set `Require SSL` to `none` by following the steps in [configuring SSL for a realm](https://www.keycloak.org/docs/latest/server_admin/#_ssl_modes).
4. Restart the Identity service again. Identity should now start successfully.

:::warning
We would only recommend that requirements for SSL are disabled in a development environment.
Expand Down
10 changes: 5 additions & 5 deletions ...docs/version-8.5/self-managed/identity/troubleshooting/troubleshoot-identity.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -74,19 +74,19 @@ When the Keycloak service is ready for connections, start (or restart) the Ident
### Solution 2: Identity making requests from an external IP address

By default, Keycloak requires TLS on requests that originate from what it considers to be an external source. The Keycloak
documentation for [setting up SSL](https://www.keycloak.org/docs/latest/server_admin/#_ssl_modes) maintains
a list of what they consider to be an external IP address under the `external requests` section.
documentation for [configuring SSL for a realm](https://www.keycloak.org/docs/latest/server_admin/#_ssl_modes) maintains
a list of what Keycloak considers to be an external IP address in the `external requests` section.

The solution to this issue will depend largely on your environment. However, as a starting point we would suggest you consider
these options:

1. Configure the communication between the services (for example in a cluster) to use IP ranges that fall within the
ranges that Keycloak expects.
2. If configuring the IP ranges is not an option, it is possible to disable the SSL requirement in Keycloak itself by completing the following steps:
1. In the `master` realm, set `Require SSL` to `none` by following the steps in [SSL modes](https://www.keycloak.org/docs/23.0.1/server_admin/#_ssl_modes).
1. In the `master` realm, set `Require SSL` to `none` by following the steps in [configuring SSL for a realm](https://www.keycloak.org/docs/latest/server_admin/#_ssl_modes).
2. Restart the Identity service.
3. In the `camunda-platform` realm, set `Require SSL` to `none` by following the steps in [SSL modes](https://www.keycloak.org/docs/23.0.1/server_admin/#_ssl_modes).
4. Restart the Identity service again. Identity should now start successfully
3. In the `camunda-platform` realm, set `Require SSL` to `none` by following the steps in [configuring SSL for a realm](https://www.keycloak.org/docs/latest/server_admin/#_ssl_modes).
4. Restart the Identity service again. Identity should now start successfully.

:::warning
We would only recommend that requirements for SSL are disabled in a development environment.
Expand Down
10 changes: 5 additions & 5 deletions ...docs/version-8.6/self-managed/identity/troubleshooting/troubleshoot-identity.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -74,19 +74,19 @@ When the Keycloak service is ready for connections, start (or restart) the Ident
### Solution 2: Identity making requests from an external IP address

By default, Keycloak requires TLS on requests that originate from what it considers to be an external source. The Keycloak
documentation for [setting up SSL](https://www.keycloak.org/docs/latest/server_admin/#_ssl_modes) maintains
a list of what they consider to be an external IP address under the `external requests` section.
documentation for [configuring SSL for a realm](https://www.keycloak.org/docs/latest/server_admin/#_ssl_modes) maintains
a list of what Keycloak considers to be an external IP address in the `external requests` section.

The solution to this issue will depend largely on your environment. However, as a starting point we would suggest you consider
these options:

1. Configure the communication between the services (for example in a cluster) to use IP ranges that fall within the
ranges that Keycloak expects.
2. If configuring the IP ranges is not an option, it is possible to disable the SSL requirement in Keycloak itself by completing the following steps:
1. In the `master` realm, set `Require SSL` to `none` by following the steps in [SSL modes](https://www.keycloak.org/docs/23.0.1/server_admin/#_ssl_modes).
1. In the `master` realm, set `Require SSL` to `none` by following the steps in [configuring SSL for a realm](https://www.keycloak.org/docs/latest/server_admin/#_ssl_modes).
2. Restart the Identity service.
3. In the `camunda-platform` realm, set `Require SSL` to `none` by following the steps in [SSL modes](https://www.keycloak.org/docs/23.0.1/server_admin/#_ssl_modes).
4. Restart the Identity service again. Identity should now start successfully
3. In the `camunda-platform` realm, set `Require SSL` to `none` by following the steps in [configuring SSL for a realm](https://www.keycloak.org/docs/latest/server_admin/#_ssl_modes).
4. Restart the Identity service again. Identity should now start successfully.

:::warning
We would only recommend that requirements for SSL are disabled in a development environment.
Expand Down

0 comments on commit 6a5b1fe

Please sign in to comment.