Security in ASP.NET Core 2.1
summary
Covers concrete security changes in ASP.NET Core 1.0→2.1 and what's coming in 3.0: Kestrel ships HTTPS by default with dotnet dev-certs and SNI support, HSTS defaults to 30 days, guidance to keep Kestrel behind a proxy, and patch cadence of about a month. Authentication moves to a unified service with cookie validators, virtual schemes and forwarding, built‑in Azure B2C and IdentityServer templates coming after 2.2, data protection key rings for shared keys, resource‑based authorization handlers, and GDPR cookie consent and 2FA via authenticator apps.
AI-written summary · about
chapters (20)
- 0:00Intro
- 2:32Kestrel security HTTPS by default
- 4:12SNI certification selection
- 5:00Kestrel Security Configuration
- 7:06HSTS caveats HSTS is dangerous
- 9:06Authentication Options in ASPNET Core Template Support
- 10:41Individual User Accounts v2.1 Local Database
- 11:38Template Authentication Individual User Accounts
- 12:58ASPNET Core 1.x Authentication No more custom identity classes Multiple authentication middleware
- 14:12ASPNET Core 2.0 Changes Authentication is now a single service
- 14:52Adding an authentication service
- 15:36Do it yourself Cookie Authentication
- 16:29Configuring cookie middleware
- 16:50Do it yourself Caveats
- 18:03Picking auth at runtime Virtual schemes and authentication forwarding
- 20:59API Authentication The missing link
- 25:09Data Protection One stop shop for encryption
- 26:51Using Data Protection
- 33:57What should a handler return? Successful Evaluation
- 34:39Imperative Checks Evaluate your policies in code
related talks
01h 04mSecurity in ASP.NET Core 2.1
58mSecurity in ASP.NET Core 2.0
01h 01mSecurity in ASP.NET Core 2.0
01h 03mSecuring Web Applications and APIs with ASP.NET Core 2.2 and 3.0
52mSecuring 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
53mSecuring Web Applications and APIs with ASP.NET Core 2.2 and 3.0
39mA guided tour of ASP.NET core security
