HttpClient(AndroidMessageHandler) with NTLM v2 auth and Self Signed Certificate returns 401 Unauthorized

Open
#110,523 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
android, csharp

Research direction

Start at AndroidMessageHandler and the shown CustomAndroidMessageHandler.WriteRequestContentToOutput override, then reproduce the NTLM v2 flow against the self-signed and public-certificate Exchange endpoints. The empty reproduction section and missing configuration leave the failure to be narrowed down; done means explaining the differing 401 behavior and establishing whether the self-signed case can work.

Written by the indexing model from the issue text.

Description

area-System.Net.Http os-android
Description

I'm using an on-premise exchange server with NTLM v2 authentication.
When attempting to authenticate using HttpClient and AndroidMessageHandler, I encounter a 401 Unauthorized error, specifically due to a self-signed certificate. Interestingly, when using a public certificate, authentication proceeds without any issues.

Old ticket: https://github.com/dotnet/runtime/issues/102107
Issue still reproducible using .NET9

Here parts of the code:

var _httpClientHandler = new CustomAndroidMessageHandler();
var _credentials = new CredentialCache
{
{ new Uri(serverEndpoint), "NTLM", new NetworkCredential(emailEntry.Text, passwordEntry.Text)}
};
_httpClientHandler.ServerCertificateCustomValidationCallback = (sender, cert, chain, sslPolicyErrors) => { return true; };
_httpClientHandler.Credentials = _credentials;
HttpClient httpclient = new HttpClient(_httpClientHandler);
public class CustomAndroidMessageHandler : AndroidMessageHandler
{
protected override async Task WriteRequestContentToOutput(
HttpRequestMessage request,
HttpURLConnection httpConnection,
CancellationToken cancellationToken)
{
var stream = await request.Content.ReadAsStreamAsync().ConfigureAwait(false);
await stream.CopyToAsync(httpConnection.OutputStream!, 4096, cancellationToken).ConfigureAwait(false);

if (stream.CanSeek)
{
stream.Seek(0, SeekOrigin.Begin);
}
}
}

I added

<AndroidUseNegotiateAuthentication>true</AndroidUseNegotiateAuthentication>

in csproj

Reproduction Steps

.

Expected behavior

Working.

Actual behavior

401 Unauthorized.

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

Dominant language
C#
Stars
18.3k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/runtime

All issues in dotnet/runtime

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.