How to structure a Blazor web site
-
I have what I thought was a fairly simple requirement, web site (blazor) that delivers a minimal membership service. No registration (this is done by a WPF app with 1-2 users). Set up a web api to service the data and authentication requirements (done using JWT tokens) And this is where the rabbit hole opens up! Create a web app that gets its authentication from the web api and then service the data requirements. Every example i have found wants to use Entity this and Entity that with 7 different tables, registration, 2 factor security and password recovery, NONE of which I need. All I need is to get an authenticated (email and password) token from the API and include that in each subsequent request header. This already works perfectly for the WPF client but I cannot understand how it should be done for a blazor site. Any suggestions or examples would be appreciated.
Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP