Social login
SecureAuth Connect social login lets users sign in with an existing account from a supported social provider instead of creating a new username and password. SecureAuth Connect acts as a broker between your application and the social provider, handling the authentication handshake and returning an authenticated identity.
Select a provider to view setup steps, attributes, and configuration details:
Use cases
Social login fits when you want to reduce sign-up friction for consumer-facing applications.
- Consumer apps (B2C): Users sign in with an account they already have. No new password to create or remember, which reduces registration drop-off.
- Developer platforms: Let developers authenticate with GitHub or Google to access your APIs or developer portal.
- Multi-provider choice: Offer several social providers so users can pick the one they prefer. SecureAuth Connect normalizes the identity regardless of which provider the user chooses.
- Complement to other methods: Use social login as a first factor alongside passwordless methods or passkeys. Users who prefer a social account get that option; others use OTP or passkeys.
Social login is not the best fit for workforce or B2B scenarios where your organization controls the identity provider (use enterprise SSO instead), or when you need attributes that social providers do not share.
Compare providers
| Provider | What you get | Good to know |
|---|---|---|
| Apple | Email, name | Only shares data on first login. Enable JIT provisioning. |
| Email, name, profile picture | Profile picture URL included. | |
| GitHub | Email, name, login, company, groups | Most attributes. Includes organization and team memberships. |
| Email, name, email verification | Includes token metadata. Confirms email verification status. | |
| Email, name, email verification, profile picture | Professional identity with verification status and profile picture. | |
| Microsoft | Email, name, phone, job title, language | Richest business context. Attributes from both ID token and User Info. |
| X | Username, confirmed email, name | Uses X handle as username. Email returned as confirmed_email. |
How to add a social provider
The setup flow is the same for every provider:
- Go to Authentication > Providers > Create Connection.
- Select a social provider.
- Choose Embedded (zero-config, uses SecureAuth's app registration) or Bring your Own (uses your organization's app registration).
- Click Save, then configure attributes, mappings, and provisioning.
Each provider's page includes detailed registration steps, default attribute mappings, and provisioning options.