NTLM Authorization

[DavidM29]

Hello,

I have been searching, but I have not been able to find how to use NTLM Authorization when using OData Connected Service DataServiceContext.

Only way I have found for now is to ConfigureHttpClientDefaults like this:

builder.Services.AddHttpClient();
builder.Services.ConfigureHttpClientDefaults(clientBuilder =>
{
    clientBuilder.ConfigurePrimaryHttpMessageHandler(() =>
    {
        string domain = string.Empty;
        string serviceUsername = ApplicationSettings.ServiceUsername;
        string servicePassword = ApplicationSettings.ServicePassword;

        if (serviceUsername.Contains('\\'))
        {
            var domainAndUser = serviceUsername.Split('\\');
            domain = domainAndUser[0];
            serviceUsername = domainAndUser[1];
        }

        HttpClientHandler handler = new HttpClientHandler();
        handler.Credentials = new NetworkCredential(serviceUsername, servicePassword, domain);
        return handler;
    });
});

and then use the IHttpClientFactory with the DataServiceContext.

This works well, but my issue with it is that I have to configure the default HttpClients generated by the IHttpClientFactory to use NTLM Authorization, so now if I want to use a HttpClient without the NTLM Authorization, I have to use a named HttpClient. I think It would be more convenient if we were able to use named HttpClients with DataServiceContext.

Originally posted by @DavidM29 in #3248

[gathogojr]

Thank you @DavidM29 for reporting the issue. Is there a reason you'd prefer to go with named HttpClient or can use make use of a delegate handler passed to the OData client that would configure the HTTP client when it's created. We'd like to look at the best way to support your scenario.

[DavidM29]

Hello @gathogojr,
The problem I am facing right now is that, I have a blazor app, where default HttpClient is used by a third-party component library. I do not know how or where in the library it is used, so I would prefer not to touch it and mess up how the component library works.

Using named HttpClient would solve all the problems, because I can configure it the way I have configured the default HttpClient above.

I also think that using named HttpClient in the DataServiceContext would need less changes than exposing a delagate and using that, but I am not sure.

[DavidM29]

@gathogojr, is this something that I can expect to be worked on in the foreseeable future? I have not had a chance to contribute to an open source project yet, but implementing named HttpClient support seems fairly straightforward so I could try to work on it if you decide to go with that.
However if this is something that is going to end up in the backlog, then I have to go with a different approach as time is not on my side at the moment.