Demystifying Web API Security in Azure
summary
Demo builds a .NET 8 API and two clients, registers apps in Entra ID (Azure AD), and implements role-based app permissions so tokens include to-do.read/to-do.write roles. Uses client credentials for service-to-service calls and rejects unauthorized writes with 403; on-behalf-of is considered but not used because tokens originate from mixed providers. Local dev and Swagger work via PKCE, production uses managed identities to avoid secrets. Infrastructure is declared with Pulumi. The setup runs end-to-end in the demo.
AI-written summary · about
chapters (12)
- 0:00Web API security challenges
- 1:12Monoliths to microservices security
- 3:18Azure AD and OAuth2 authentication
- 5:05Zero trust and internal security
- 9:16Azure AD as identity provider
- 14:39Authorizing callers with permissions
- 22:52Azure AD API security setup
- 31:42Role-based authorization in ASP.NET Core
- 46:34Securing server API demo
- 46:58External client auth demo
- 53:46Internal client auth demo
- 1:00:54Summary
related talks
52mDemystifying Web API Security in Azure
53mWeb API Security With Azure Active Directory
01h 03mBuilding Secure Microservices in Azure
01h 05mBuilding Secure Microservices in Azure
55mReal World Guide to Web API authentication on Azure
01h 03mServerless and App Service Security on Azure
41mReal World Guide to Web API authentication on Azure
50mSecuring .NET Apps and Microservices in Azure
