Social login and registration enables users to register and login to your website by using an account created on a social login identity provider (IdP) such as Facebook or Twitter. For example, instead of logging on by using an email address and password users can log on by using their Facebook account or their Twitter account.

Historically, the social login identity providers available to users was limited to the IdPs that appear in the Social Login Dashboard. If you wanted to use a different IdP, such as Slack or Spotify, well, that wasn’t impossible, but it wasn’t easy, either. And it wasn’t something that organizations could do on their own.

The Custom Providers API changed all that. Using this API, organizations can now leverage almost any social login IdP they want, as long as that identity provider uses one of the following protocols:

  • OAuth 2.0
  • OpenID Connect
  • SAML 2

Before you begin using the Custom Providers API, here are a few things to keep in mind:

  • The Custom Providers API works with most IdPs that support OAuth 2.0, OpenID Connect, or SAML 2. However, because different identity providers implement these protocols in different ways, there's no guarantee that the API works with every IdP that supports one of those protocols.

  • Custom providers can only be created – and managed – by using the API. For example, if you create a custom provider for Twitch that provider won’t be available in the Social Login Dashboard.

  • In addition to using the Custom Provider API to configure Identity Cloud, you also need to create a social login app on the IdP itself. In other words, to use Twitch as a custom IdP you need to:

    1. Get a Twitch developers account.
    2. Log in to the Twitch developers site.
    3. Create a Twitch app for social login.

See Create a SAML authentication application, which walks you through the process of creating a social login app, for more information.