I love how there are so many things I could just "borrow" from this app into my own apps based on my needs for each app. Thanks a million for building this and showing how it works and what pieces I can look for ❤️
Also super interesting to see how Auth domain it's not just a part of the application it fully drives part of the architecture, also the fact that the full show was mainly about Auth concepts proves how hard Auth can be
BFF pattern is especially good with Blazor WASM because it allows using rendering mode 'WebAssemblyPrerendered' with authentication, which is a must IMO since Blazor WASM as a SPA takes noticeable longer to load than JS frameworks. This requires jumping through some hoops but is totally worth it for that instant html content.
Lots of good conversation regarding AuthN/AuthZ. I think the other elephant in the room - besides the reality that not everybody can, or even should, use OIDC - is that some software companies allow their web application software to sprawl across two or more subdomains, instead of using a reverse proxy from the outset and diligently operating on a single domain (or single subdomain). Suddenly using cookies for authentication becomes untenable because of the CORS requirements. But cookies have come a long way now, with various security controls around their transmission, and being able to set a cookie in a modern browser that is implicitly transmitted as part of each request is very powerful. A bit of a shame I think.
Glad to see a second video on the TodoApi ( first one was by Raw Coding I think ) , Context it's a big part of Software design so it's important to know the context that drove the creator of the api to code it that way
