Skip to content

Commit 8a8bd0e

Browse files
authored
Update csi-secrets-store-identity-access.md
1 parent 829be3d commit 8a8bd0e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/aks/csi-secrets-store-identity-access.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to integrate the Azure Key Vault Provider for Secrets Sto
44
author: nickomang
55
ms.author: nickoman
66
ms.topic: article
7-
ms.date: 12/01/2023
7+
ms.date: 12/19/2023
88
ms.custom: devx-track-azurecli, devx-track-linux
99
---
1010

@@ -25,7 +25,7 @@ You can use one of the following access methods:
2525

2626
## Access with a Microsoft Entra Workload ID
2727

28-
A [Microsoft Entra Workload ID][workload-identity] is an identity that an application running on a pod uses to authenticate itself against other Azure services, such as workloads in software. The Storage Store CSI Driver integrates with native Kubernetes capabilities to federate with external identity providers.
28+
A [Microsoft Entra Workload ID][workload-identity] is an identity that an application running on a pod uses to authenticate itself against other Azure services, such as workloads in software. The Secret Store CSI Driver integrates with native Kubernetes capabilities to federate with external identity providers.
2929

3030
In this security model, the AKS cluster acts as token issuer. Microsoft Entra ID then uses OIDC to discover public signing keys and verify the authenticity of the service account token before exchanging it for a Microsoft Entra token. For your workload to exchange a service account token projected to its volume for a Microsoft Entra token, you need the Azure Identity client library in the Azure SDK or the Microsoft Authentication Library (MSAL)
3131

0 commit comments

Comments
 (0)