Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Key Vault auth policy specifies tenant ID for token requests #19841

Closed
chlowell opened this issue Jan 18, 2023 · 1 comment
Closed

Key Vault auth policy specifies tenant ID for token requests #19841

chlowell opened this issue Jan 18, 2023 · 1 comment
Labels
Client This issue points to a problem in the data-plane of the library. feature-request This issue requires a new behavior in the product in order be resolved. KeyVault
Milestone

Comments

@chlowell
Copy link
Member

Once azcore/policy.TokenRequestOptions has a TenantID field (part of #17159), Key Vault's auth policy should set that field and update its value upon receiving a challenge, so that token requests always specify the correct tenant. This is a low priority because a vault's tenant changes only when that vault moves to a new tenant, a vanishingly rare scenario that can currently be handled by creating a new client after the move.

@chlowell chlowell added KeyVault Client This issue points to a problem in the data-plane of the library. labels Jan 18, 2023
@chlowell chlowell added this to the Backlog milestone Jan 18, 2023
@chlowell chlowell added the feature-request This issue requires a new behavior in the product in order be resolved. label Jan 19, 2023
@gracewilcox
Copy link
Member

Tracked in #22928

@github-actions github-actions bot locked and limited conversation to collaborators Sep 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. feature-request This issue requires a new behavior in the product in order be resolved. KeyVault
Projects
None yet
Development

No branches or pull requests

2 participants