OpenID Connect Architectural Patterns
summary
Demo shows implemented OpenID Connect flows using .NET 9 with pushed authorization requests, shows SSO working across two web apps and exposes the problem: naive logout only clears the app cookie and users immediately reauthenticate; solution uses end_session redirect with ID token hint and back-channel logout to revoke sessions when Safari blocks third‑party cookies (affects ~30% of users). Also builds a federation gateway that brokers Android ID / Microsoft Entra ID / custom providers and compares tenant models (single issuer with tenant claim vs separate issuer per tenant).
AI-written summary · about
chapters (14)
- 0:00OpenID Connect patterns
- 3:21Basic auth flow
- 7:07Single sign-on and sessions
- 9:58Single logout challenge
- 13:08CSRF protection in logout
- 16:03Post-logout redirect URIs
- 22:51Safari cookie restrictions
- 25:05Back-channel logout
- 30:10Federation gateway pattern
- 34:30Federated sign-out complexity
- 39:14Identity provider selection UX
- 43:09Multi-tenancy patterns
- 49:29Entra ID multi-tenant handling
- 50:36Summary of patterns
related talks
57mBuilding Clients for OpenID Connect/OAuth 2-based Systems
54mOpenID Connect In Depth
47mWho's your user? OpenID from the ground-up
58mOAUTH, OPENID CONNECT & .NET – THE GOOD PARTS
39mSecuring your apps with OAuth2 and OpenID Connect
31mAuthentication with OpenID Connect in Angular Applications
54mWho's your user? OpenID from the ground-up
58mBuilding JavaScript and mobile/native Clients for Token-based Architectures
