Module
Module 3 of 5Lesson 1 of 2~15 min

OpenID Connect and signing in with Google, Apple or Microsoft

Lesson 1 of the module "Delegating sign-in" in the course "Design authentication and permissions for a product".

Take this lesson: your first course is freeSee the full syllabus

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.

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

  1. OpenID Connect and signing in with Google, Apple or Microsoft (this lesson)
  2. Enterprise SSO, SAML, OIDC and SCIM provisioning

What you will learn in the course

This lesson is part of the course Design authentication and permissions for a product

  • Distinguish authentication, authorization and session, and specify session durations, sign-out and access revocation.
  • Specify password rules and account recovery journeys following current recommendations (NIST SP 800-63B-4, CNIL, OWASP).
  • Choose strong authentication factors (TOTP app, passkeys), plan their rollout and specify the fallback journeys.
  • Specify delegated sign-in (OpenID Connect, social login) and enterprise SSO (SAML, OIDC, SCIM provisioning) for a B2B product.
  • Design a permission model (roles, attributes, scope) as a roles × actions matrix, enforced on the server side according to least privilege.
  • Specify isolation between customers, invitations, the audit log, support access and account deletion.
  • Specify your product's complete sign-in journeys, with states and errors, and choose between building and using an authentication provider.

Related courses