Demystifying Web API Security in Azure
summary
Shows a concrete migration path: a .NET 8 API deployed to Azure, provisioned with Pulumi, using Microsoft.Identity.Web for token validation and Azure AD application roles to enforce action-level permissions. External on‑prem clients use client credentials (client id + secret), Azure-hosted services use managed identity to avoid secrets. On‑behalf-of flows prove infeasible for mixed on‑prem systems, so a roles+client‑credentials model is implemented and tested end‑to‑end and works for the demo.
AI-written summary · about
chapters (10)
- 0:00Introduction to API security
- 2:28Microservices architecture challenges
- 5:59Zero trust security model
- 10:32Authentication for internal services
- 16:11Authorization for healthcare data
- 22:14Demo setup and Azure AD config
- 36:26Role-based authorization in practice
- 40:43External client authentication
- 47:27Managed identities in Azure
- 51:25Key takeaways and Q&A
related talks
01h 02mDemystifying Web API Security in Azure
01h 05mBuilding Secure Microservices in Azure
53mWeb API Security With Azure Active Directory
01h 03mBuilding Secure Microservices in Azure
50mSecuring .NET Apps and Microservices in Azure
55mReal World Guide to Web API authentication on Azure
41mReal World Guide to Web API authentication on Azure
58mLet's talk Auth
