No sign-in authentication handlers are registered. Did you forget to call AddAuthentication().AddCookie("Identity.Application",...)? was logged when SignInManager.PasswordSignInAsync ran in an app that had called AddAuthentication() but registered no cookie handler for Identity. Register the Identity cookies with AddAuthentication(IdentityConstants.ApplicationScheme).AddIdentityCookies().

With AddIdentityCore the cookies are not part of the registration, so this line has to be added by hand. In the lab, with no AddAuthentication() call at all, the same login failed with a different message first, about IAuthenticationSchemeProvider.

The error

The request curl.exe -s -i -X POST -H "Content-Type: application/json" -d "@register.json" http://127.0.0.1:15620/login got HTTP/1.1 500 Internal Server Error, and the server console logged:

fail: Microsoft.AspNetCore.Server.Kestrel[13]
...
      System.InvalidOperationException: No sign-in authentication handlers are registered. Did you forget to call AddAuthentication().AddCookie("Identity.Application",...)?
...

Why it happens

The registration in that run had authentication services but no handler:

...
builder.Services.AddAuthentication();
builder.Services.AddIdentityCore<IdentityUser>()
    .AddEntityFrameworkStores<AppDb>()
    .AddSignInManager();
...
app.MapPost("/login", async (LoginBody body, SignInManager<IdentityUser> signIn) =>
{
    var result = await signIn.PasswordSignInAsync(body.Email, body.Password, false, false);
    return result.ToString();
});
...

The message names the scheme Identity.Application, and this registration had no handler for it; the fixed run below set a cookie named after that scheme. One run earlier, without the AddAuthentication() line, the same request got a 500 with:

...
      System.InvalidOperationException: Unable to resolve service for type 'Microsoft.AspNetCore.Authentication.IAuthenticationSchemeProvider' while attempting to activate 'Microsoft.AspNetCore.Identity.SignInManager`1[Microsoft.AspNetCore.Identity.IdentityUser]'.
...

So the two messages are two steps of the same missing setup. Both broken runs answered the client with an empty 500 (Content-Length: 0), so the text is only in the server log; a client that shows only the status code gives no hint of the cause.

The fix

...
builder.Services.AddAuthentication(IdentityConstants.ApplicationScheme)
    .AddIdentityCookies();
builder.Services.AddIdentityCore<IdentityUser>()
    .AddEntityFrameworkStores<AppDb>()
    .AddSignInManager();
...

The same request then answered HTTP/1.1 200 OK with the body Succeeded and a Set-Cookie: .AspNetCore.Identity.Application=... header (value cut here). Using the full AddIdentity registration instead was not run for this login.

The lab's endpoint passes false as the last argument of PasswordSignInAsync, which switches lockout counting off for that call; a real sign-in endpoint passes true so that repeated wrong passwords lock the account. Only false was run here.

How it was reproduced

A dotnet new web -f net10.0 project on .NET SDK 11.0.100 with Microsoft.AspNetCore.Identity.EntityFrameworkCore 10.0.10 and Microsoft.EntityFrameworkCore.Sqlite 10.0.10, a seed that creates one fictional user, and a /login endpoint. The body file (named register.json because the test's runner posts that file) held {"email":"tomas.silva@example.test","password":"Spring-2026x"}; IdnLab, port 15620, /login, the user, the password, AppDb and lab.db are the test's; a real seed reads a password from configuration or user-secrets, never from source. Three logged runs (the first run of the fix was not logged and was repeated), each built with dotnet build and started with dotnet bin\Debug\net10.0\IdnLab.dll --urls http://127.0.0.1:15620 (Hosting environment: Production), the request sent from the project folder: no authentication call (a new copy of the base project; the evidence records no lab.db before it), AddAuthentication() alone, and the fix; the later runs moved the previous file aside first.

Frequently asked

How do I fix No sign-in authentication handlers are registered?
Register the Identity cookies: builder.Services.AddAuthentication(IdentityConstants.ApplicationScheme).AddIdentityCookies(). In the lab PasswordSignInAsync then succeeded and set the Identity.Application cookie.
Why does PasswordSignInAsync fail with AddIdentityCore?
In the lab AddIdentityCore with AddSignInManager registered no authentication handler. Without AddAuthentication the error named IAuthenticationSchemeProvider; with AddAuthentication() alone it was No sign-in authentication handlers are registered.
Where does the sign-in handler error appear?
On the request: the client got an empty 500 and the server console logged the InvalidOperationException under Microsoft.AspNetCore.Server.Kestrel.

Registering Identity twice gives 'Scheme already exists: Identity.Application'. More decoded errors in the Fixes category.