-
ABP Framework version: v9.0.1
-
UI Type: Blazor
-
Database System: EF Core (SQL Server)
We are experiencing issues with Blazor WASM initialization due to the loading of modules.
We considered using InteractiveAuto rendering to speed up the initial load of the login page when the user is not authenticated, but this is not an option since our component suite is designed to work with WASM.
We have explored alternatives, such as having two WASM projects referenced from the same Blazor WebApp project (Blazor, Blazor.Client, Blazor.Login), as demonstrated here:
https://github.com/jirisykora83/WebAppMultiBlazor
We want to apply this same approach using ABP, with the idea that the additional Blazor.Login project would handle authentication. This project would only include authentication dependencies and the login page to streamline the initial entry into the application.
In other words, when the user is not authenticated, they should be redirected to the login page of the Blazor.Login project. If authenticated, they should be redirected to the Blazor.Client project, which contains all application dependencies and represents the main application.
Would this be possible with ABP? What logic would need to be overridden to achieve this approach?
Thank you very much!
1 Answer(s)
-
0
Hi
You can try implementing it yourself, ABP only provides standard templates, I can help you If you get any problems in implementation
