IdentityServer for ASP.NET Core 2
summary
IdentityServer4 adapts to ASP.NET Core 2 by replacing the old auth plumbing with dependency-injected handlers so a single middleware picks the default scheme and you can swap cookie or bearer handlers; built-in cookie and external Google handlers work out of the box and community packages add WS‑Fed and SAML2P support. The Azure AD flow uses an OpenID Connect state caching workaround to avoid 2KB URL limits. Co-hosted APIs use bearer tokens, logout supports front/back-channel patterns, templates and an Admin UI speed setup, and production support and contribution paths are provided.
AI-written summary · about
chapters (19)
- 0:00Intro
- 2:00New Authentication System
- 3:40Authentication Methods
- 5:00Middleware
- 5:44Passive middleware
- 8:08Handlers
- 8:40Authentication middleware
- 9:04Default authentication schemes
- 10:09The 5 methods
- 17:50DFS support
- 20:54SAML support
- 26:52Open ID Connect
- 29:37Hestia Handler
- 30:36API Handler
- 37:17Logout
- 38:57FrontChannel
- 45:09Templates
- 51:49Contributing
- 53:45Training Consulting
related talks
01h 00mIdentityServer4: New & Improved for ASP.NET Core
58mIdentityServer4: New & Improved for ASP.NET Core
54mSecuring Web Applications and APIs with ASP.NET Core 2.2 and 3.0
01h 03mIdentity Server 4 with Angular and ASP.NET Core
01h 01mSecuring Web Applications and APIs with ASP.NET Core 2.2 and 3.0
58mSecurity in ASP.NET Core 2.0
51mAuthentication and Authorization in ASP.NET Core 2
01h 04mImplementing Authentication and Authorization with ASP.NET Core 2
