Blazor and jwt problems with Scaffold Identity

[Rick-Anderson]

Moved from #7633 by @sbsw
These pages sometimes say we should use services.AddDefaultIdentity, and sometimes services.AddIdentity. Reading between the lines, AddIdentity exposes additional options for configuring Identity. But there is no coherent description of the difference between these two methods. We really need a section early in this documentation that presents these two registration methods and information about the follow-on fluent methods that are required and/or optional.

Put a link to this comparison in:

• Content: Scaffold Identity in ASP.NET Core projects
• Content Source: aspnetcore/security/authentication/scaffold-identity.md

Per Hao
AddDefaultIdentity is just syntactic sugar for the old code that used to be in startup + AddDefaultUI, whatever you are trying to do,

See AddDefaultIdentity

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: d3ac09f0-74ca-1a5d-4fec-695b84c1ac95
• Version Independent ID: cd2c1f5e-e4f0-d2c3-4737-8ff4f0c176c2
• Content: Configure ASP.NET Core Identity
• Content Source: aspnetcore/security/authentication/identity-configuration.md
• Product: aspnet-core
• GitHub Login: @AdrienTorris
• Microsoft Alias: riande

[pholly]

This is great. In addition to docs, I also looked at samples in the AspNet/Identity repo and Visual Studio templates and found it confusing which overload to use.

[raffaeler]

All the 2.1 External Providers configuration documentation pages were not updated to 2.1
For example, the Microsoft Account page does not mention the mandatory .AddDefaultUI() and still mention the old ApplicationUser. The correct one is the following:

services.AddIdentity<IdentityUser, IdentityRole>()
    .AddEntityFrameworkStores<ApplicationDbContext>()
    .AddDefaultTokenProviders()
    .AddDefaultUI();

https://docs.microsoft.com/en-us/aspnet/core/security/authentication/social/microsoft-logins?view=aspnetcore-2.1&tabs=aspnetcore2x

This should be changed for the other external providers as well.

[talldaniel]

I think that is not called syntactic sugar, but is called a breaking change.

[ussiemer]

the Scatfolding is a mess too - the whole blazor identity is not very Full Stack friendly right now... suddenly I have empty .js in wwwroot/Identity and such... I guess I will write a own Identity template. But for my project it consumes now time - razor pages was clean and simple this tries to be super nice and timesaving but leads me to problems and stress...

[bernatgy]

I have the same problems as @Scobiform. This "version" of Identity is completely confusing. Even the docs. In my opinion docs SHOULD NOT start with the assumption that everyone wants to start using it with a whole bunch of abstract default settings, Entity Framework, MVC and whatnot. I've only just started researching because I want to implement something super simple, and I've already been reading for 2 hours without knowing anything about how I should start using it and how and what I should override (either types or options).