Blazor Authentication? Hold My Beer!
summary
Explains concrete recipes for cookie + OpenID Connect in Blazor Server, WebAssembly and Auto (hybrid): use authorization code flow with a server-side token store, proactive refresh via Duende.AccessTokenManagement, and a BFF (back end for front end) that issues same-site strict session cookies. Shows code hooks: implement token store interface, register Duende.BFF and map BFF endpoints, or proxy external APIs with YARP and an access token HTTP client. Demos login, claims and API calls working end-to-end.
AI-written summary · about
chapters (8)
- 0:00Blazor auth challenges
- 4:27Blazor auth modes
- 8:47Blazor Server auth
- 17:12Blazor WASM auth
- 21:34BFF pattern with Blazor
- 36:44Blazor Auto mode auth
- 42:03Blazor auth data access
- 55:24Q&A
related talks
57mAuthentication and Authorization in Blazor
01h 03mSecuring SPAs and Blazor Applications using the BFF (Backend for Frontend) Pattern
01h 02mUsing the BFF pattern to secure SPA and Blazor Applications
28mMicrosoft, Google and Cookie Authentication and Authorization
57mSecuring SPAs and Blazor Applications using the BFF (Backend for Frontend) Pattern
01h 02mSecuring SPAs and Blazor Applications using the BFF (Backend for Frontend) Pattern
59mThe whirlwind tour of Authentication and Authorization with ASP.NET Core
01h 04mImplementing Authentication and Authorization with ASP.NET Core 2
