diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/oidc-examples.md b/deploy-manage/users-roles/cluster-or-deployment-auth/oidc-examples.md index 22e23d869b..df9c3644a8 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/oidc-examples.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/oidc-examples.md @@ -86,7 +86,7 @@ For more information about OpenID connect in Azure, refer to [Azure OAuth 2.0 an op.token_endpoint: "https://login.microsoftonline.com//oauth2/v2.0/token" op.userinfo_endpoint: "https://graph.microsoft.com/oidc/userinfo" op.endsession_endpoint: "https://login.microsoftonline.com//oauth2/v2.0/logout" - rp.post_logout_redirect_uri: "KIBANA_ENDPOINT_URL/logged_out" + rp.post_logout_redirect_uri: "KIBANA_ENDPOINT_URL/security/logged_out" op.jwkset_path: "https://login.microsoftonline.com//discovery/v2.0/keys" claims.principal: email claim_patterns.principal: "^([^@]+)@YOUR_DOMAIN\\.TLD$" @@ -284,7 +284,7 @@ For more information about OpenID connect in Okta, refer to [Okta OAuth 2.0 docu It will typically be `/api/security/oidc/callback`. If you're using {{ech}}, then set this value to `/api/security/oidc/callback`. - 6. Set the **Logout redirect URI** as `KIBANA_ENDPOINT_URL/logged_out`. + 6. Set the **Logout redirect URI** as `KIBANA_ENDPOINT_URL/security/logged_out`. 7. Choose **Done** and copy your client ID and client secret values for later use. 2. Add your client secret [to the {{es}} keystore](/deploy-manage/security/secure-settings.md). @@ -367,4 +367,4 @@ Remember to add this configuration for each node type in the [User settings](../ description: "Log in with Okta" basic.basic1: order: 1 - ``` \ No newline at end of file + ```