Add an OAuth 2.0 Identity Provider
This guide explains how to register a generic OAuth 2.0 identity provider (IdP) in ThunderID. Use this type for OAuth 2.0 providers that do not implement OpenID Connect discovery. If the provider supports OIDC, use Add an OIDC Identity Provider instead.
Prerequisites
- ThunderID is running. See Get Started.
- You can sign in to the ThunderID Console.
- A client application registered in the external OAuth 2.0 provider with a Client ID, Client Secret, and redirect URI.
- The provider's authorization endpoint, token endpoint, and userinfo endpoint URLs.
Create the OAuth 2.0 Connection
Step 1: Add a Custom Connection
- Sign in to the ThunderID Console.
- Navigate to Connections.
- Click the Add custom connection card.
Step 2: Choose the Connection Type
- On the Connection type step, click OAuth 2.0 Provider.
- Click Continue.
Step 3: Configure the Connection
Enter the following fields, then click Create connection:
| Field | Required | Description |
|---|---|---|
| Connection name | Yes | A friendly name used to identify this connection. |
| Client ID | Yes | The client ID issued by the OAuth 2.0 provider. |
| Client secret | Yes | The client secret issued by the OAuth 2.0 provider. |
| Authorization endpoint | Yes | The provider's authorization endpoint, used to start the sign-in flow. |
| Token endpoint | Yes | The provider's token endpoint, used to exchange the authorization code for tokens. |
| UserInfo endpoint | Yes | The provider's userinfo endpoint. ThunderID calls this endpoint to fetch the authenticated user's profile. |
| Scopes | No | Space-separated OAuth scopes to request. |
The Redirect URI field is read-only. Copy its value and register it as the callback URL with your provider.
The connection also accepts logoutEndpoint and prompt fields, and an attributeConfiguration field to map this provider's claims to local user attributes. These are not available in the Console and can only be set through the Connections API. See Attribute Configuration for the mapping concepts, which apply the same way to OAuth 2.0 connections.
Next Steps
- Connect an IdP to an Application: Add this OAuth 2.0 IdP to an application's authentication flow.
- Manage Identity Providers: Update or delete identity providers.