I love building great products to help businesses succeed in their goals. I currently work at Okta as a Developer Support. I work with Authentication and authorization every day. My work here is a beautiful intersection of hard skills and soft skills. I resolve customer’s most complex problems revolving around our platform products. In my free time, I enjoy biking, yoga, and surfing… Surfing the internet that is.
How can application developers provide users with secure authentication without investing a lot of time and instead focus on building their application’s core functionality? With OpenId Connect (OIDC) you give the authority to a trusted provider to prove that the user is who they say they are. OIDC is built on top of OAuth 2.0 so it has all functionality of OAuth 2.0 plus more. In this talk, We explore how do applications talks to each other to get access to resources on behalf of the user via OIDC. We will also walk through how to get access and Id token with OpenId Connect.
- What is OAuth 2.0 and what problem does it solve
- What is OIDC and why was it built on top of OAuth
- What is the difference between authentication and authorization
- walk-through of How to get JSON web token using OpenID Connect flow