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

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

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more