Let's talk Auth
summary
A centralised auth site takes an Azure B2C OpenID Connect token, maps external identity into an internal account and issues JWT signed tokens that APIs accept as Bearer. An ASP.NET Core WebAPI plugs in middleware that intercepts JWTs, calls an Azure Functions for token validation (verifies signature and cancellable state), and populates a scoped user service so controllers read a simple user.Name. Demo shows configuration, DI registration, and ordering needed to make the pipeline work.
AI-written summary · about
chapters (10)
- 0:00Start
- 9:18Central Authentication Mechanism
- 14:11Json Web Tokens
- 24:00Json Web Token Authentication Extension
- 26:04Validating Tokens
- 30:32Configure Services
- 36:39Web Hooks
- 37:04Functions
- 47:33Adding Custom Middleware
- 57:34Questions
related talks
59mThe whirlwind tour of Authentication and Authorization with ASP.NET Core
51mAuthentication and Authorization in ASP.NET Core 2
01h 04mImplementing Authentication and Authorization with ASP.NET Core 2
41mEasy-Auth: The Easiest Way to Secure Your Application in Azure App Service
57mASP.NET Core Authentication and Authorization - the Key Concepts
54mOpenID Connect In Depth
50mSecuring .NET Apps and Microservices in Azure
52mDemystifying Web API Security in Azure