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

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
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