No sign-out authentication handlers are registered. Did you forget to call AddAuthentication().AddCookie("Identity.Application",...)?

[pantonis]

When I call signInManager.SignOutAsync I get No sign-out authentication handlers are registered. Did you forget to call AddAuthentication().AddCookie("Identity.Application",...)?
I have googled the issue and found that you need to add .AddCookie(o =>....) in Startup.cs

Why would someone need to add cookie when it is working only with JWT and localstorage???

Further technical details

• ASP.NET Core version 5.0.5
• Include the output of dotnet --info
• The IDE (VS / VS Code/ VS4Mac) you're running on, and its version VS2019

[blowdart]

There's no signout mechanism for JWT, the identity is not persisted between calls, you send it every time. So why would you need to signout?

I don't know what "local storage" is referring to here.

[pantonis]

@blowdart regarding the signout you are correct.
@blowdart local storage refers to document in a browser.
However I was getting the same error when I was calling signInManager.PasswordSignInAsync until I understood that this method is used only with cookies. In the official documentation there is no such clarification except for the explanation of the isPersistent param which after 3 hours of searching I found that you need to use the signInManager.CheckPasswordSignInAsync when working with IdentityCore and jwt.

[blowdart]

But we don't supply local storage logins, unless this is a blazor issue?

SigninManager is part of aspnet identity which does use cookie and sets it all up for you.

[pantonis]

From all this conversation you only understood that the issue is with local storage?

…

On Tue, 27 Apr 2021, 19:21 Barry Dorrans, ***@***.***> wrote: But we don't supply local storage logins, unless this is a blazor issue? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#32215 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZEO3QFCKXHOQCT4SZJUNLTK3QCPANCNFSM43VDA2NQ> .

[blowdart]

From this conversation it's not clear how local storage plays into any of this. SignInManager is for ASP.NET Identity. ASP.NET identity does not use client-side local storage. ASP.NET Identity does not use JWT. So where are you using SignInManager, what type of project?

[ghost]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

See our Issue Management Policies for more information.