[KeyVault] Externalize ChallengeBasedAuthenticationPolicy token cache#5518
Merged
sophiajt merged 1 commit intoAzure:masterfrom Oct 13, 2019
Merged
Conversation
schaabs
approved these changes
Oct 10, 2019
sophiajt
approved these changes
Oct 13, 2019
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes an issue reported in #5021 which states that the
ChallengeBasedAuthenticationPolicyis authenticating with AAD for every request to the KeyVault service instead of reusing the original access token that it received. The fix is to use a similar approach to PR #4174 and store the token cache externally becauseRequestPolicyinstances get recreated for each request incore-http.The changes for all 3 file are identical because this class is currently duplicated across the
@azure/keyvault-*libraries.Fixes #5021.