Fix NullReferenceException when using BasicHttpBinding and NTLM web proxy authentication #4555
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.
Fixed Check for SecurityTokenManager initialization for web proxies with NTLM authentication:
When using BasicHttpClient Bindings with additional authentication for enterprise style web proxies, a NullReferenceException was raised because of missing initialization of SecurityTokenManager (resulting member field was NULL).
By extracting the AuthenticationScheme passed by the used binding and using it for deciding whether SecurityTokenManager is needed or not, the NRE is removed and NTLM auth can be used successfully within the HTTP channel factory.