Philippe De Ryck
page-template,page-template-full_width,page-template-full_width-php,page,page-id-728,bridge-core-3.0.2,qode-page-transition-enabled,ajax_fade,page_not_loaded,,vertical_menu_enabled, vertical_menu_hidden,vertical_menu_hidden_with_logo, vertical_menu_width_260,qode-title-hidden,side_menu_slide_with_content,width_470,qode-theme-ver-28.8,qode-theme-bridge,disabled_footer_top,qode_header_in_grid,wpb-js-composer js-comp-ver-6.9.0,vc_responsive

Philippe De Ryck

Introduction to OAuth 2.0 and OpenID Connect

OAuth 2.0 is likely one of the most complex aspects of modern web applications. It is often mistakenly assumed that OAuth 2.0 offers authentication and authorization. Instead, OAuth 2.0 only offers delegation. To make matters more complicated, there are at least six different OAuth 2.0 flows, each for a particular purpose. On top of that, OpenID Connect (OIDC) redefines some of these flows to enable authentication explicitly.

In this talk, we will clear up the confusion about OAuth 2.0 and OIDC. We will explain the purpose and properties of most relevant flows. We explore how to use OAuth 2.0’s delegation mechanism to enable authorization on a backend. Finally, we will look at using OIDC for end-user authentication with a third-party provider. At the end of this talk, you will have a solid understanding of OAuth 2.0/OIDC and how to use it in your applications.

About Philippe De Ryck

Founder of Pragmatic Web Security, Google Developer Expert

Philippe De Ryck is the founder of Pragmatic Web Security, where he travels the world to train developers on web security and security engineering. He holds a Ph.D. in web security from KU Leuven. Google recognizes Philippe as a Google Developer Expert for his knowledge of web security and security in Angular applications.