Key Vault: Ensure cached tokens are used during authentication #2382
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.
In non-interactive environments we cannot show an auth dialog, so we need to ensure that silent auth is being used (fixes #2105). In addition, in certain configurations users have seen the KV cmdlets report that "credentials have not been set up or have expired". This is caused by not using the serialized cache from AzureContext.TokenCache. The changes in this PR are based off of the code in AuthenticationFactory, but due to our use of a Hyak-based client, we cannot use the existing functions. Once we adopt autorest, we can remove this code and use the shared implementation.