Skip to content
  • Auth and access
  • Social connections

Add and manage social connections

Social connections enable you to sign up and sign in users with credentials from their existing social accounts, such as Google or GitHub.

An advantage of social sign in is that users don’t have to create new credentials to use your app or service, making it more convenient and secure for them.

If they have a gravatar picture associated with their social account, it will flow through to Kinde.

Set up a social connection

Link to this section

Follow the docs below for each social provider you want to use. This will give you the Client ID and Client secret (keys) you need to set up each auth method on the Kinde side.

You can also add Custom OAuth 2.0 connections via the same Social connections area. Custom OAuth2 connections now support configuring the client authentication method (body vs. header) for the token exchange — see the Custom OAuth 2.0 connection guide for details.

When an email is not provided

Link to this section

Some social providers don’t require an email for sign up, e.g. X. When a user signs up or in with one of these providers, Kinde will ask for an email (just once). This is so we can verify the user’s identity and be sure it’s a genuine sign up.

We treat social identities different to email identities in Kinde, and record social providers as a social identity in their user profile. For more information, see User identity and verification.

Trusting emails from social providers

Link to this section

Under Provisioning, configure the connection as follows: Set Email address trust to Trust only when you know the third-party provider verifies email addresses and does not allow users to change their primary email address. For a safer middle ground, select Verify, then trust. Google social connections are set to Trust by default. For details about the options, see Trusting emails from providers.

Delete a social connection

Link to this section
  1. In Kinde, go to Settings > Environment > Authentication.
  2. Scroll down to the Social connections section and select the three dots on the tile for the connection, then select Delete connection.
  3. In the confirmation window, select Delete connection.

Can I display conditional social login options?

Link to this section

No, Kinde’s hosted authentication screens do not support conditional show/hide logic for social sign-in buttons based on the user’s device platform. For example, it is not possible to hide the Apple sign-in button for Android users or hide the Google sign-in button for iOS users. All configured social connections are shown to all users on the hosted auth screen regardless of device.

If you need platform-conditional authentication options, consider building custom authentication pages where you have full control over which buttons are rendered.

Manage social connections via API

Link to this section

You can add, update, and delete social connections via the Kinde management API using predefined endpoints.

Set the connection’s email address trust with the trust_mode option when you create or update a connection. It accepts none (Don’t trust), validate (Verify, then trust) or trust (Trust). The older is_trusted boolean is deprecated but still accepted: true maps to trust and false to none, and trust_mode wins if both are sent. If neither is sent, Google connections default to trust and all other strategies default to none. Responses include both trust_mode and a derived is_trusted.