OpenID Connect and signing in with Google, Apple or Microsoft
Your users ask for a sign in with Google or Microsoft button, but that choice affects account security. This lesson helps you understand what OpenID Connect adds to OAuth 2.0, decide whether social login is worth it for your product, and specify its rules without opening a security hole.
Lesson objective
By the end of this lesson, you will be able to explain what OpenID Connect adds to OAuth 2.0, decide whether your product offers social login and with which providers, and specify the account linking rules that prevent account takeovers.
Topics covered
- OpenID Connect
- OAuth 2.0
- social login
- sign in with Google
- identity provider
In the glossary
Where it fits
Delegating sign-in
When should you let Google, Microsoft or a company's directory authenticate your users, and what do you need to specify?
Lessons in this module
- OpenID Connect and signing in with Google, Apple or Microsoft (this lesson)
- Enterprise SSO, SAML, OIDC and SCIM provisioning
What you will learn in this module
This lesson is part of the course Design authentication and permissions for a product
- Specify delegated sign-in (OpenID Connect, social login) and enterprise SSO (SAML, OIDC, SCIM provisioning) for a B2B product.
Related courses
- Product ManagementAdvancedRegular practice: you already use the tools or work on this topic.
Git for PMs: ship as a team without putting production at risk
3 hr 30 min
- Tech for PMsAll levelsNo prerequisites: accessible to everyone.
Explain how a web product works, from browser to server
2 hr 30 min
- Tech for PMsJuniorSome basics are useful: introductory knowledge of the topic.
Design and test an API integration as a PM
3 hr