On this page

Add a social Identity Provider

This document explains how to configure

as an external social Identity Provider (IdP) for your application by creating an application on
, creating an Identity Provider in Okta, testing the configuration, and creating a sign-in button.

Okta manages the connection to the IdP for your application, sitting between your application and the IdP that authenticates your users. The industry-standard term for this is Inbound Federation. When a user signs in, you can link the user’s

account to an existing Okta user profile or choose to create a new user profile using Just-In-Time (JIT) provisioning.

Note: We also support additional services such as directories and credential providers. See the Okta Integration Network Catalog (opens new window) to browse all integrations by use case.

Learning outcomes

Configure a social Identity Provider so that your users can quickly sign up or sign in to your application by using their social Identity Provider account.

What you need

Create an app at the Identity Provider

  1. When you create an application at the IdP, you need to provide a redirect URI for authentication.

    The redirect URI sent in the authorize request from the client needs to match the redirect URI set at the IdP. This URI is where the IdP sends the authentication response (the access token and the ID token). It needs to be a secure domain that you own. This URI has the same structure for most IdPs in Okta and is constructed using your Okta subdomain and the callback endpoint.

    For example, if your Okta subdomain is called company, then the URI would be https://company.okta.com/oauth2/v1/authorize/callback. If you have configured a custom domain in your Okta org, use that value to construct your redirect URI, such as https://login.company.com/oauth2/v1/authorize/callback.

  2. Save the generated

    client ID and client secret values. You need them to configure your Identity Provider in Okta.

Create the Identity Provider in Okta

To add

as an Identity Provider in Okta:

  1. In the Admin Console, go to Security > Identity Providers.

  2. Click Add Identity Provider, and then select


  3. Click Next.

  4. In the General Settings section, define the following:

    • Name: Enter a name for the Identity Provider in Okta.
    • Client ID: Paste the generated client ID from your
    • Client Secret: Paste the generated client secret from your
    • Scopes: Leave the defaults for a simple sign-in flow. You can also add more scopes. See .
  5. Click Finish.

Test the integration

You can test your integration by configuring a routing rule (opens new window) to use

as the Identity Provider.

Alternatively, you can use the Authorize URL to simulate the authorization flow. The Okta Identity Provider that you created generated an authorize URL with a number of blank parameters that you can fill in to test the flow with the Identity Provider. The authorize URL initiates the authorization flow that authenticates the user with the Identity Provider.

In the URL, replace ${yourOktaDomain} with your org's base URL, and then replace the following values:

  • client_id: Use the client_id value from your Okta app integration. This is not the client_id from the Identity Provider. For example, 0oawjqpb2wcUAWM8C0h7.

  • response_type: Determines which flow is used. For the Implicit flow, use id_token. For the Authorization Code flow, use code.

  • response_mode: Determines how the authorization response is returned. Use fragment.

  • scope: Determines the claims that are returned in the ID token. Include the scopes that you want to request authorization for and separate each with a %20 (space character). You need to include at least the openid scope. You can request any of the standard OpenID Connect scopes about users, such as profile and email as well as any custom scopes specific to your Identity Provider.

  • redirect_uri: The location where Okta returns a browser after the user finishes authenticating with their Identity Provider. This URL must start with https and must match one of the redirect URIs that you configured in the previous section.

  • state: Protects against cross-site request forgery (CSRF). This can be set to any value.

  • nonce: A string included in the returned ID token. Use it to associate a client session with an ID token and to mitigate replay attacks. This can be set to any value.

For a full explanation of all of these parameters, see: /authorize Request parameters.

An example of a complete URL looks like this:


Add the Identity Provider to the Okta Sign-In Widget

Note: This section is only for Okta Classic Engine. If you are using Okta Identity Engine, the Sign in with IdP option is available on the widget after you've created the Identity Provider in your Okta org and configured the routing rule (opens new window). No additional code is required. See Identify your Okta solution (opens new window) to determine your Okta version and see Upgrade your widget for upgrade considerations to Identity Engine.

The Okta Sign-In Widget (opens new window) is an embeddable JavaScript widget that reproduces the look and behavior of the standard Okta sign-in page. You can add a Sign in with

button to the widget by adding the following code to your Okta Sign-In Widget configuration. Replace Your_IDP_ID with the Identity Provider ID from your Identity Provider that you created in Okta in the Create the Identity Provider in Okta section.

To find your Identity Provider ID:

  1. In the Admin console, go to Security > Identity Providers.
  2. On the Identity Providers page, select the Identity Provider tab.
  3. Select your Identity Provider from the list. IdP ID contains your Identity Provider ID.

Next steps

You should now understand how to add a social Identity Provider and have successfully added and tested the integration.

To map Okta attributes to app attributes, use the Profile Editor (opens new window).

To add another Identity Provider, start by choosing an external Identity Provider.