Google Login lets a domain's users sign in to the Hub with their Google Workspace account instead of (or alongside) a Hub password. It is handled entirely by the shared federation framework's generic SAML strategy — there is no Google-specific route, Passport strategy, or code; Google Workspace is simply configured as a SAML 2.0 identity provider (IdP), identically to any other SAML IdP.
Microsoft Login lets a domain's users sign in to the Hub with their Microsoft Entra ID (formerly Azure AD) account instead of (or alongside) a Hub password. Like Google Login, it is handled entirely by the shared federation framework's generic SAML strategy — Microsoft Entra ID is simply configured as a SAML 2.0 identity provider (IdP), with no Microsoft-specific route, Passport strategy, or code.
The Hub supports single sign-on via a shared federation framework (5app/hub, auth/modules/federation/). Every provider — LinkedIn OAuth2/OIDC, or any SAML 2.0 identity provider — is resolved dynamically, per request, from the domain's configuration; there is no per-provider route or Passport strategy registered up front. This page documents the mechanics shared by every provider. Provider-specific setup lives on its own page: