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

Popular posts from this blog

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…

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.