Azure / Azure/azure-workload-identity

Detailed documentation on requesting AAD tokens for Service account tokens.

Open
#354 0 comments 1 reaction 0 assignees View on GitHub
documentation
Dominant language
Go
Stars
337
Forks
122
Avg merge
1h 7m
Merged PRs (30d)
3

Description

This is more of a request for documentation to explain the internal flow for service account tokens exchange for AAD tokens.

Referring to below link[1] to understand the  "Azure AD Workload Identity" to retrieve AAD tokens for an Kubernetes pod workload, where its mentioned as Kubernetes workload would be sending projected, signed service account token to Azure Active Directory to request access token to access cloud resources. And Azure Active Directory will communicate with OIDC endpoint to validate service account JWT. But How does Kubernetes workload(pod) be sending service account token to Azure AD and how does Azure AD understand the service account JWT. I feel, this information is not clear and upon researching over the internet, I haven't found much details.

[1] https://azure.github.io/azure-workload-identity/docs/

For example, the link below[2] is related to the same user case and it has explained how the Pod Service account token has been passed to Vault and how Vault is able to communicate with the OIDC endpoint and how vault token has been provided to Pod. Can we get this level of detailed information over any sources or in Azure AD Workload Identity documentation.

[2] https://banzaicloud.com/blog/kubernetes-oidc/

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the Azure Workload Identity documentation at https://azure.github.io/azure-workload-identity/docs/ and compare it with the Kubernetes OIDC example at https://banzaicloud.com/blog/kubernetes-oidc/. Trace how a pod presents its projected service account JWT, how Azure AD validates it through the OIDC endpoint, and how the access token is returned. Done means the documentation explains this exchange at the requested level of detail.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, kubernetes
Domain
authentication, cloud, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.