AspNetCore.Docs
AspNetCore.Docs copied to clipboard
dotnet
Need detail about Build Identity components under Blazor Server Identity
[EDIT by guardrex to add the metadata. @Rick-Anderson ... I'll take care of this one. It's for the Blazor remarks in the Scaffolding doc.]
This part needs to be detailed,"SignInManager and UserManager aren't supported in Razor components" is well questioned. Code samples are needed like how to build API controller to be used in Identity Razor components, especially for external login such as Microsoft for Razor Component, since I've realized basic login/out. The scaffold stuff is understandable, just feels weird when using different UI stuff. It will be better if we can keep building front in razor component when handling identity.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: 804e24dd-7e30-8cf5-2c99-1ffacb4582f6
- Version Independent ID: 3e25547b-e2c9-6634-2c38-2a77207f17d4
- Content: Scaffold Identity in ASP.NET Core projects
- Content Source: aspnetcore/security/authentication/scaffold-identity.md
- Product: aspnet-core
- Technology: aspnetcore-security
- GitHub Login: @Rick-Anderson
- Microsoft Alias: riande
Hello @Kumima ... FYI, please use the The page feedback buttom and form from the bottom of any US-English topic to open issues here. It will add metadata about the topic and ping the author automatically. I'll manually add the metadata to your opening comment.
WRT your remarks: The product unit has indicated that they prefer (for the time being) not to provide auth-based Razor components, and they have told developers why SignInManager/UserManager aren't supported.
WRT more info on API endpoints, this text can cross-link this to the Blazor security docs. These API endpoints would be no different than any other secured server API endpoints. More info is found throughout the node, too, because this is a common use case scenario for providers, such as AAD, B2C, IdS: https://docs.microsoft.com/aspnet/core/blazor/security/ ... but building out the components themselves is up to developers to do on their own or via a 3rd party package/library. Check Awesome Blazor, search the Net, and ask on public forums.
Cross-references:
- https://github.com/dotnet/aspnetcore/issues/34095
- https://github.com/dotnet/aspnetcore/issues/21199
- https://github.com/dotnet/aspnetcore/issues/13601
- https://github.com/dotnet/aspnetcore/issues/11411
... and there are several other issues with similar remarks.
Leave this issue open. I would like to investigate explaining the remark in the article further, possibly with a cross-link to that first product unit issue. This issue will close automatically when the PR is merged later.
I'll be quite busy ⛰️⛏️😅 through the end of the year with .NET 7 documentation. I'll probably reach this in 23Q1.
