From f4d57ef9190ca86e7dc0409687b3c7d8d33fe6ba Mon Sep 17 00:00:00 2001 From: Lydia Pedersen Date: Mon, 9 Jan 2023 11:42:48 -0800 Subject: [PATCH 1/2] ENDOC-640 --- vuepress/docs/next/docs/consume/identity-management.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vuepress/docs/next/docs/consume/identity-management.md b/vuepress/docs/next/docs/consume/identity-management.md index a7f95f0aa8..cef4e7ea06 100644 --- a/vuepress/docs/next/docs/consume/identity-management.md +++ b/vuepress/docs/next/docs/consume/identity-management.md @@ -31,7 +31,7 @@ Keycloak authorizes microservices using clients and roles. Authorizations are st Below are the steps to grant a user one or more roles for a specific client. This controls permissions when configuring the microservice. Note: when a microservice is installed in Entando, a corresponding client (and set of roles) is created per its plugin definition. -1. [Login to your Keycloak instance](#logging-into-your-keycloak-instance) +1. [Login to Keycloak](#logging-into-your-keycloak-instance), which for non-external Keycloak instances is [the base URL of your running Entando application](../getting-started/README.md#configure-access-to-your-cluster) followed by `/auth/`, e.g. http://YOUR-HOST-NAME/auth. In a standard Entando installation, the base URL can be verified with `kubectl get ingress/default-sso-in-namespace-ingress`. 2. Select `Users` from the menu on the left 3. Use the search box to find the appropriate user, e.g. "admin" 4. Click on the user ID From c4e73916c26afaf804f084f71e2e671b06957b50 Mon Sep 17 00:00:00 2001 From: Lydia Pedersen Date: Mon, 9 Jan 2023 14:17:04 -0800 Subject: [PATCH 2/2] ENDOC-640 Add to 7.1 --- vuepress/docs/v7.1/docs/consume/identity-management.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vuepress/docs/v7.1/docs/consume/identity-management.md b/vuepress/docs/v7.1/docs/consume/identity-management.md index a7f95f0aa8..cef4e7ea06 100644 --- a/vuepress/docs/v7.1/docs/consume/identity-management.md +++ b/vuepress/docs/v7.1/docs/consume/identity-management.md @@ -31,7 +31,7 @@ Keycloak authorizes microservices using clients and roles. Authorizations are st Below are the steps to grant a user one or more roles for a specific client. This controls permissions when configuring the microservice. Note: when a microservice is installed in Entando, a corresponding client (and set of roles) is created per its plugin definition. -1. [Login to your Keycloak instance](#logging-into-your-keycloak-instance) +1. [Login to Keycloak](#logging-into-your-keycloak-instance), which for non-external Keycloak instances is [the base URL of your running Entando application](../getting-started/README.md#configure-access-to-your-cluster) followed by `/auth/`, e.g. http://YOUR-HOST-NAME/auth. In a standard Entando installation, the base URL can be verified with `kubectl get ingress/default-sso-in-namespace-ingress`. 2. Select `Users` from the menu on the left 3. Use the search box to find the appropriate user, e.g. "admin" 4. Click on the user ID