Identity Providers
An identity provider (IdP) in ThunderID represents an external system that authenticates users on your behalf. When you integrate an IdP, users can sign in to your applications using their existing accounts with that provider, for example, their Google or GitHub account.
ThunderID supports four IdP types.
| Type | Use Case |
|---|---|
| Sign in with Google accounts. Endpoints are pre-configured. Requires only your Google OAuth client credentials. | |
| GitHub | Sign in with GitHub accounts. Endpoints are pre-configured. Requires only your GitHub OAuth app credentials. |
| OIDC | Connect any standard OpenID Connect-compliant provider. You supply the endpoints. |
| OAuth | Connect any OAuth 2.0 provider that does not support OIDC discovery. You supply all endpoint URLs. |
How IdPs Connect to Applications
Applications in ThunderID do not reference IdPs directly. The connection runs through authentication flows:
- You configure the IdP as a connection on the Console's Connections page.
- You add a social login executor to an authentication flow and configure it with the IdP.
- You assign that flow to your application.
When a user signs in to the application, ThunderID runs the assigned flow, which triggers the IdP's authorization redirect.
See Connect an IdP to an Application for the full walkthrough.
Set Up an Identity Provider
Choose the guide for your provider type:
- Add a Google Identity Provider
- Add a GitHub Identity Provider
- Add an OIDC Identity Provider
- Add an OAuth 2.0 Identity Provider
Manage Identity Providers
- Manage Identity Providers: View, update, and delete identity providers from the ThunderID Console.
Next Steps
- Connect an IdP to an Application: Wire a configured IdP into an application's sign-in flow.
- Build a Sign-In Flow: Learn how to customize authentication flows in the Flow Designer.
