Securing your apps with OAuth2 and OpenID Connect
summary
Explains why classic username/password pages fail for modern SPAs and native apps, demonstrates a .NET stack using IdentityServer3 and sample .NET clients, and shows tokens issued as JSON Web Token (JWT) with discoverable public keys, a revoke page and support for authorization code, implicit and hybrid flows. Covers refresh tokens (offline_access scope), token claims and scopes, how the resource server validates tokens, and a live demo calling a protected API.
AI-written summary · about
chapters (7)
- 0:00Introduction and speaker intro
- 0:46Problem with current authentication
- 10:50OAuth2 roles and token flow
- 20:13OAuth2 flows explained
- 25:36OpenID Connect benefits
- 30:18Demo of IdentityServer
- 36:26Q&A session
related talks
59mSecuring Web APIs from JavaScript/SPA Applications
01h 05mCommon mistakes and misconceptions in Web App Security using OAuth 2.0 and OpenId Connect
57mBuilding Clients for OpenID Connect/OAuth 2-based Systems
58mBuilding JavaScript and mobile/native Clients for Token-based Architectures
01h 02mModern Authentication
58mOAUTH, OPENID CONNECT & .NET – THE GOOD PARTS
37mOAuth2 and OpenID Connect for Single Page Applications
01h 00mOAuth – the good Parts
