Authentication with OpenID Connect in Angular Applications
summary
Argues that authentication should be delegated to an identity provider via OpenID Connect and shows concrete flows: hybrid flow (id_token + code) for backends, front-ends using PKCE to avoid storing secrets, implicit flow deprecated. Demonstrates Netlify+GitHub example, obtains id token and access token to call APIs, and says common libraries like angular-oauth2-oidc or Auth0/Keycloak adapters handle the ugly redirect and token exchange so an Angular app often needs under a hundred lines of configuration to get working.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:23Authentication
- 4:23OpenID Connect
- 8:33Private Use
- 10:25Delegate Authentication
- 23:14How to write code
- 26:38Session management
- 27:21Identity brokering
- 28:11Enterprise identity brokering
- 29:42Wrap up
related talks
54mOpenID Connect In Depth
39mLogin and Access Control in Angular
37mOAuth2 and OpenID Connect for Single Page Applications
57mBuilding Clients for OpenID Connect/OAuth 2-based Systems
01h 02mBuilding Clients for OpenID Connect/OAuth 2-based Systems
47mIntroduction to OAuth 2.0 and OpenID Connect
28mOAuth 2.0 and OIDC
27mIntegrating API Security Into A Comprehensive Identity Platform