Skip to main content

InvalidOperationException: No authenticationScheme was specified, and there was no DefaultChallengeScheme found.

Sometimes, you have of these days where you stumble from one issue to another. This was (unfortunately) one of these days. The story started when I tried to run an ASP.NET Core project I had to review. (Always my first check, can I follow the instructions in the readme.md file and get the source code up and running easily on my local machine).

But this day, no luck, as ASP.NET Core decided to give me the following error message:

InvalidOperationException: No authenticationScheme was specified, and there was no DefaultChallengeScheme found.

Typically this indicates that no authentication is configured, but a look at the Program.cs file didn’t bring me closer to the solution. Everything looked okay:

Then I noticed the following in my Visual Studio, I was running the application through Kestrel.

Could that be the reason? I switched to IIS Express and ran the application again. Now I was able to start the application succesfully.

Enabling Windows Authentication for Kestrel

Does this mean that Windows authentication is not supported for Kestrel? Since ASP.NET Core 3.1 it is. Windows Authentication can be configured for ASP.NET Core apps hosted with IIS, Kestrel, or HTTP.sys.

Let’s see how to get this done.

First we need to install the Microsoft.AspNetCore.Authentication.Negotiate NuGet package. This package is required to support Windows Authentication with Kestrel.

We update our application bootstrapping logic to use this authentication package:

Next we need to update our launchsettings.json. We add an extra authenticationMode setting and set it to Windows.

If we now run the application again through Kestrel, the error should be gone and we can succesfully authenticate through our Windows credentials.

More information: https://docs.microsoft.com/en-us/aspnet/core/security/authentication/windowsauth?view=aspnetcore-6.0&tabs=visual-studio#enable-windows-authentication-with-httpsys

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more