Skip to content

Commit d8b5358

Browse files
Add troubleshooting guide for external identity provider authentication to AKS
1 parent 2a95f87 commit d8b5358

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

support/azure/azure-kubernetes/security/troubleshoot-aks-control-plane-authentication-external-identity-providers.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ This article helps you troubleshoot authentication issues when accessing the Azu
2222

2323
- Azure CLI version 2.61.0 or later. To find the version run `az --version` . If you need to install or upgrade, see [Install Azure CLI](/cli/azure/install-azure-cli).
2424
- A tool to connect to the Kubernetes cluster, such as the `kubectl` tool. To install `kubectl` using the Azure CLI, run the [az aks install-cli](/cli/azure/aks#az-aks-install-cli) command.
25-
- The JWT authenticator configuration file used for your AKS cluster.
25+
- The JSON Web Token (JWT) authenticator configuration file used for your AKS cluster.
2626
- Access to [jwt.ms][jwt-ms] or a similar JWT token decoder tool for debugging tokens.
2727

2828
## Troubleshooting checklist
@@ -263,7 +263,7 @@ The OAuth client or OIDC provider settings are incorrect.
263263

264264
1. Go to the [Google Cloud Console](https://console.cloud.google.com).
265265
2. Navigate to **APIs & Services** > **Credentials**.
266-
3. Verify the OAuth 2.0 client ID and ensure redirect URIs are correct.
266+
3. Verify the OAuth 2.0 client ID and secrets.
267267

268268
::: zone-end
269269

@@ -294,7 +294,7 @@ CEL expressions might have syntax errors or return unexpected data types.
294294

295295
**Cause: Cluster nodes cannot reach the identity provider**
296296

297-
Network security groups, firewalls, or DNS issues prevent the cluster from accessing the identity provider.
297+
Network security groups, firewalls, or Domain Name System (DNS) issues prevent the cluster from accessing the identity provider.
298298

299299
#### Solution 1: Verify DNS resolution
300300

0 commit comments

Comments
 (0)