Skip to content

Commit 3deedc9

Browse files
authored
Merge pull request #15638 from MicrosoftDocs/main
8/7/2024 PM Publish
2 parents c222e86 + 960303c commit 3deedc9

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

AKS-Hybrid/ad-sso.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Use Active Directory single sign-on for secure connection to Kubernetes A
33
description: Use Active Directory Authentication to securely connect to the API server with SSO credentials
44
author: sethmanheim
55
ms.topic: how-to
6-
ms.date: 06/24/2024
6+
ms.date: 08/07/2024
77
ms.author: sethm
88
ms.lastreviewed: 1/14/2022
99
ms.reviewer: sulahiri
@@ -30,7 +30,10 @@ AD integration uses AD kubeconfig, which is distinct from the certificate-based
3030
Another security benefit with AD integration is that the users and groups are stored as [security identifiers (SIDs)](/troubleshoot/windows-server/identity/security-identifiers-in-windows). Unlike group names, SIDs are immutable and unique and therefore present no naming conflicts.
3131

3232
> [!NOTE]
33-
> Currently, AD SSO connectivity is only supported for workload clusters.
33+
> AD SSO connectivity is only supported for workload clusters.
34+
35+
> [!NOTE]
36+
> The use of nested AD groups (creating an AD group within another AD group) is unsupported.
3437
3538
This article guides you through the steps to set up Active Directory as the identity provider and to enable SSO via `kubectl`:
3639

0 commit comments

Comments
 (0)