Want to learn more about OAuth 2.0 and OpenID Connect?
Save yourself days of digging through dozens of specs with this online courseMore information
Passwords and pixie dust - A look at OAuth 2.0 security in Angular
This page contains the resources for the talk titled 'Passwords and pixie dust - A look at OAuth 2.0 security in Angular'.
OAuth 2.0 is a complex beast. The original OAuth 2.0 specification introduces four different flow, each with their respective use cases. Since its release, one of the flows has been deprecated, and a few additional flows have been proposed. But which flow is right for an Angular application? Which flow should you stay away from? And more importantly, why are some flows considered to be insecure?
In this talk, we give a brief overview of a few flows within OAuth 2.0. From a high-level point of view, we point out their use cases and differences. In the second part, we dive into a recent addition, PKCE ('pixie'). This new PKCE-based flow enhances the security properties for OAuth 2.0 flows for public clients. Everyone working with OAuth 2.0 should be aware of it, and use it when available.
Dr. Philippe De Ryck
Hi, I'm Philippe, and I help developers protect companies through better web security. As the founder of Pragmatic Web Security, I travel the world to teach practitioners the ins and outs of building secure software.
Talks and workshops
Security is often about small nuances. In my articles, I dive deeper into various security topics, providing concrete guidelines and advice. My articles also answer questions I often get while speaking or teaching.
Getting security right is all about knowledge. I strongly believe in sharing that knowledge to move forward as a community. Among my resources, you can find developer cheat sheets, recorded talks, and extensive slide decks.
Subscribe to the Pragmatic Web Security mailing list to stay up to date on the latest activities and resources.