Add authentication management with a login page in the admin project.

[mariovh-fnet]

Would it be possible to manage authentication for the entire application within the admin project? Either in a simulated way or by using the WebApp project as the server?

The idea is that if the user is not authenticated at any point in the application, they would be redirected to the login page of the Admin project, which would be lighter and have minimal dependencies. The user would enter their credentials there and then be redirected to the Web project, where the heavier part of the application resides.

We are experiencing delays in Blazor initialization as the number of modules increases, and your solution structure with multiple Blazor WASM projects might be the answer to our issues. Since they are independent, we could centralize authentication in a lightweight, standalone project.

Do you think this would be viable?

Thank you very much, and great work!

[jirisykora83]

I am not sure if the proposed solution makes sense. As users in the end have to download a and run "heavier" application so he may (not sure) get login page faster. But only if server itself redirects to login page (?again not sure). And i think make it to works how you describe may be difficult (i am definitely not expert on authorization/authentication 😅)

From my point of view flow which you proposing will works like this

user download app A --> user/device run app A --> device/app decided it required login & redirect to app B --> ... user downlaod/run/login in app B ---> redirect to app A (and have to "run" app A again

i think it must be slower.

My recommendation would be to check what makes app A start slower. If you are really motivated MS is currently working on a new profiler (dotnet/runtime#112352) and it maybe be possible to test it soon.

Out of curiosity is your application publicly available?