Hao Kung

its a bit stale let me make sure it still works :)

I don't really recall, could we have just upgraded package versions?

I'm not sure there are any existing providers but you should be able to implement your own identity store using EF Core

Discussion issue for this announcement: https://github.com/dotnet/aspnetcore/discussions/23728

Note: we have also removed all of the remaining unused classes/apis related to the old 1.x authentication stack in https://github.com/aspnet/AspNetCore/commit/d7a7c65b2b40a97bb0ba78c07380c46bc5920400 This includes: ```C# // Classes Microsoft.AspNetCore.Http.Authentication.AuthenticationManager Microsoft.AspNetCore.Http.Authentication.AuthenticateInfo Microsoft.AspNetCore.Http.Authentication.AuthenticationProperties Microsoft.AspNetCore.Http.Features.Authentication.AuthenticateContext Microsoft.AspNetCore.Http.Features.Authentication.ChallengeContext...

I'm guessing the code in the cookie handler hasn't changed too much since Katana days (@Tratcher can confirm), but LoginPath appears to only be used in two places: https://github.com/aspnet/AspNetKatana/blob/dev/src/Microsoft.Owin.Security.Cookies/CookieAuthenticationHandler.cs#L287 Its...

So there's a difference between not authenticated and not authorized, once they have logged in, you need to send them to a "You are not authorized to view this page"...

The validation interval should just be delaying when the loop happens

So usually roleManager.Create will do the normalization of the role name for you, the question is why its not able to find the role with the normalized role name in...

Also did you scaffold out any/all of the identity UI pages?