Social Login (OAuth) Settings

Configure your social login (OAuth) settings from the Descope Console under Settings → Authentication Methods → Social Login.

Enable Method in API and SDK

The Enable method in API and SDK toggle controls whether OAuth authentication can be invoked programmatically via APIs and SDKs.

• When enabled: Authentication works via flows, APIs, and SDKs
• When disabled: Authentication only works with flows or calls made with a valid management key

This global setting applies to all OAuth providers. Individual providers can have their own overrides for this setting.

Connection Settings

Every OAuth provider will have a Connection Settings section that allows you to configure the provider's connection details. This section will include the provider's client ID, client secret, and redirect URI.

In addition, you'll be able to configure other settings specific to the provider, such as the Prompt and whether or not to use PKCE.

User Attribute Mapping

The User Attribute Mapping section allows you to map the user attributes from the provider to the user attributes in your application.

For example, if the provider returns an email attribute, you can map it to the email attribute in your application.

Every OAuth provider will allow you to map any attributes from the provider's id_token or /userinfo endpoint.

Provider-Specific Settings

Each OAuth provider has its own configuration options that vary depending on whether you're using:

• Default providers (e.g., Google, Microsoft, GitHub) - See the default providers documentation.
• Custom providers - See the custom providers documentation.

For detailed configuration instructions, refer to the documentation for your specific provider type.