Replies: 3 comments
-
It's quite problematic if we want to just use it as backend and frontend on separate react/nextjs elsewhere. Microsoft Documentation is really lacking on this part, plus I'm rather new to dotnet. |
Beta Was this translation helpful? Give feedback.
-
The approach taken in the template is based on the standard SPA templates coming in .NET 8; https://devblogs.microsoft.com/dotnet/asp-net-core-updates-in-dotnet-8-preview-5/#authentication-and-authorization. This helps to reduce the complexity of the template, since I don't need to build anything to support security and identity. The documentation relating to security and identity hasn't been updated for .NET 8. When it is released, you will find the documentation here; https://learn.microsoft.com/en-us/aspnet/core/security/?view=aspnetcore-8.0. If you want to try logging into ASP.NET Core Identity using .http files, try adding the following requests to the existing WebApi.http file:
The goal of the template is to demonstrate the simplest approach to Clean Architecture with ASP.NET Core. If anyone has suggestions on how I can make security and identity simpler, please let me know. ❤️ |
Beta Was this translation helpful? Give feedback.
-
The latest PR does exactly that for the API template; #939. 💥 |
Beta Was this translation helpful? Give feedback.
-
Will it be possible to add Auth related WebApi only controllers for the WebApi variant? No razor pages or stuff, but pure API Controllers in optimal way.
Beta Was this translation helpful? Give feedback.
All reactions