This repository has been archived by the owner on Jan 19, 2021. It is now read-only.
Use DefaultNetworkCredentials if the current credentials should be used #2076
Conversation
This file contains 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Type
Related Issues?
This issue has been discovered while using PR #2068 in our Azure DevOps scripts for an on premises environment.
What is in this Pull Request ?
If a script is started with CurrentCredentials, the Credentials object of the context is empty. This causes an issue with REST based calls that construct their own
HttpClient, as theUseDefaultCredentialsflag on each instance of theHttpClienthas to be set. As an alternative, the Credentials object can be set on the context to theCredentialCache.DefaultNetworkCredentialswhich is the same as using theUseDefaultCredentialsflag.