You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/azure/azure-kubernetes/security/troubleshoot-aks-control-plane-authentication-external-identity-providers.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ This article helps you troubleshoot authentication issues when you access the Az
23
23
- Azure CLI version 2.61.0 or later. To determine the version, run `az --version`. If you have to install or upgrade, see [Install Azure CLI](/cli/azure/install-azure-cli).
24
24
- A tool to connect to the Kubernetes cluster, such as the `kubectl` tool. To install `kubectl` by using Azure CLI, run the [az aks install-cli](/cli/azure/aks#az-aks-install-cli) command.
25
25
- The JSON Web Token (JWT) authenticator configuration file that's used for your AKS cluster.
26
-
- Access to [jwt.ms][jwt-ms] or a similar JWT token decoder tool for debugging tokens.
26
+
- Access to [jwt.ms](https://jwt.ms) or a similar JWT token decoder tool for debugging tokens.
27
27
28
28
## Troubleshooting checklist
29
29
@@ -227,7 +227,7 @@ Review the AKS API server logs for authentication errors. Follow these steps:
227
227
228
228
The audience claim in the token doesn't match the configured audience in the JWT authenticator.
229
229
230
-
### Solution: Update the authenticator configuration
230
+
**Solution: Update the authenticator configuration**
231
231
232
232
Verify the audience claim in your token, and update the JWT authenticator configuration.
233
233
@@ -243,15 +243,15 @@ az aks jwtauthenticator update \
243
243
244
244
The issuer URL in the configuration doesn't exactly match the `iss` claim in the token.
245
245
246
-
### Solution: Correct the issuer URL
246
+
**Solution: Correct the issuer URL**
247
247
248
248
Update the issuer URL in your JWT authenticator configuration file to match the exact issuer in your tokens, including the protocol (https://) and any trailing slashes.
249
249
250
250
**Cause 3: Identity provider misconfiguration**
251
251
252
252
The OAuth client or OIDC provider settings are incorrect.
253
253
254
-
### Solution: Verify identity provider settings
254
+
**Solution: Verify identity provider settings**
255
255
256
256
::: zone pivot="github"
257
257
@@ -274,7 +274,7 @@ The OAuth client or OIDC provider settings are incorrect.
274
274
275
275
CEL expressions might have syntax errors or return unexpected data types.
276
276
277
-
### Solution: Verify CEL expressions
277
+
**Solution: Verify CEL expressions**
278
278
279
279
1. Review the CEL expressions in your configuration.
280
280
2. Test expressions by using a CEL evaluator to make sure that they return strings for username and arrays of strings for groups.
@@ -297,7 +297,7 @@ The following code is an example of a valid CEL expression for extracting groups
297
297
298
298
Issues that affect network security groups, firewalls, or the DNS prevent the cluster from accessing the identity provider.
299
299
300
-
### Solution 1: Verify DNS resolution
300
+
**Solution 1: Verify DNS resolution**
301
301
302
302
1. Connect to a cluster node by using `kubectl debug`:
303
303
@@ -323,7 +323,7 @@ Issues that affect network security groups, firewalls, or the DNS prevent the cl
323
323
324
324
::: zone-end
325
325
326
-
### Solution 2: Update network security rules
326
+
**Solution 2: Update network security rules**
327
327
328
328
1. Review network security group rules that are associated with your AKS cluster.
329
329
2. Make sure that outbound HTTPS (port 443) traffic is allowed to your identity provider's domain.
@@ -335,7 +335,7 @@ Issues that affect network security groups, firewalls, or the DNS prevent the cl
335
335
336
336
To prevent conflicts with other authentication methods, all usernames and groups must be prefixed by using `aks:jwt:`.
337
337
338
-
### Solution: Add the required prefix
338
+
**Solution: Add the required prefix**
339
339
340
340
Update your JWT authenticator configuration to include the `aks:jwt:` prefix. For example:
341
341
@@ -420,7 +420,7 @@ For GitHub Actions OIDC, create a file that's named `jwt-config.json` that has t
420
420
421
421
::: zone-end
422
422
423
-
1.Update the authenticator:
423
+
Update the authenticator:
424
424
425
425
```azurecli-interactive
426
426
az aks jwtauthenticator update \
@@ -442,7 +442,7 @@ To get more detailed information about authentication failures:
442
442
443
443
### Resources
444
444
445
-
-[jwt.ms site](https://jwt.ms)
445
+
-[jwt-ms token decoder tool](https://jwt.ms)
446
446
-[Supported resource logs for Microsoft.ContainerService/managedClusters](/azure/aks/monitor-aks-reference#supported-resource-logs-for-microsoftcontainerservicemanagedclusters)
447
447
448
448
[!INCLUDE [Azure Help Support](~/includes/azure-help-support.md)]
0 commit comments