Identity Server 4 with Angular and ASP.NET Core
summary
Shows a working production setup that uses IdentityServer4 + ASP.NET Core + Entity Framework with ASP.NET Identity to issue JWTs signed by a real certificate, an Angular SPA hosted inside MVC, and an API that validates tokens and enforces a MerchantAPIKeys scope. Implements multiple EF Core DbContexts and migrations, a custom client store and profile service, server-side refresh handling (refresh token never sent to client) and uses refresh token reuse to avoid race conditions — it works end-to-end.
AI-written summary · about
chapters (17)
- 0:00Introduction and overview
- 2:57Startup architecture
- 4:37Why ASP.NET Core
- 7:36Security and identity
- 12:37System demonstration
- 16:30Configuring ASP.NET Identity
- 19:25Setting up IdentityServer
- 22:13Certificates and databases
- 24:49Defining resources
- 30:20Client configuration
- 35:50Protecting the API
- 38:46Angular 2 setup
- 44:05SPA authentication flow
- 47:22Settings and data binding
- 50:06Token refresh mechanism
- 55:53SDK and consent flow
- 59:19Final thoughts and Q&A
related talks
59mBuilding APIs for developers with Identity Server 4
01h 00mIdentityServer4: New & Improved for ASP.NET Core
58mIdentityServer4: New & Improved for ASP.NET Core
55mIdentityServer for ASP.NET Core 2
54mOpenID Connect In Depth
54mSecuring Web Applications and APIs with ASP.NET Core 2.2 and 3.0
51mAuthentication and Authorization in ASP.NET Core 2
01h 04mImplementing Authentication and Authorization with ASP.NET Core 2
