Securing Web Applications and APIs with ASP.NET Core 2.2 and 3.0
summary
Overview of concrete mechanics: shows how ASP.NET Core uses an external key store and data protection keys stored outside app with automatic key rotation (new key every ~90 days) to keep cookies and tempdata valid across servers, demonstrates a working MVC+API sample using IdentityServer for tokens, implements automatic token refresh via cookie events (demo tokens set to ~70s, refresh with refresh token, revoke on sign-out), and describes the forthcoming zero‑config IdentityServer templates landing in ASP.NET Core 3.0 previews.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:43Security architecture overview
- 6:01Hosting and infrastructure
- 9:29Data protection service
- 17:19Authentication system
- 26:06External auth and tokens
- 33:00Authorization policies
- 43:23ASP.NET Core Identity
- 46:20Future and zero config
related talks
52mSecuring Web Applications and APIs with ASP.NET Core 2.2 and 3.0
01h 03mSecuring Web Applications and APIs with ASP.NET Core 2.2 and 3.0
54mSecuring Web Applications and APIs with ASP.NET Core 2.2 and 3.0
01h 01mSecuring Web Applications and APIs with ASP.NET Core 2.2 and 3.0
58mSecurity in ASP.NET Core 2.0
40mSecurity in ASP.NET Core 2.1
39mA guided tour of ASP.NET core security
01h 04mSecurity in ASP.NET Core 2.1