---
schema_version: "1"
id: 1a6bea5a94c99b1433b63317cfc30a0510b41b81dc79de5a3425fec564ff5404
title: Configure OAuth2 Providers for B2C Commerce
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/cc/264-0-0/b2c_configuring_oauth2_providers.md
canonical_url: https://help.salesforce.com/s/articleView?id=cc.b2c_configuring_oauth2_providers.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 28d1e79d29f89463ef1ac9fe6478d1213f7080e34e171b1ad6dc5d38573139aa
description: Use Business Manager to configure OAuth2 providers, but you must first register your site with your selected providers.
products:
  - Commerce
  - B2C Commerce
release: "264"
---
# Configure OAuth2 Providers for B2C Commerce

Use Business Manager to configure OAuth2 providers, but you must first register your site with your selected providers.

1. Click App Launcher ![App Launcher](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/cc/b2c_merchandiser_administrator/images/appLauncher.png), and then select **Administration** | **Global Preferences** | **OAuth2 Providers**.
2. To create a provider, click **New** or **New from Template**. To edit an existing provider record, click its ID.
    
    Google Plus has been deprecated, so don’t use the Google Plus template. For instructions on using Google, including migrating from Google Plus, see the Google developer documentation.
3. On the Global Preferences OAuth2 Providers Edit page, edit or create the following details: <table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
          <tbody><tr class="">
            <td style="vertical-align:top;" headers="d235658e70-option" id="d235658e74">Client ID</td>

            <td style="vertical-align:top;" headers="d235658e70-desc d235658e74">Obtain from the provider.</td>

          </tr>
          <tr class="">
            <td style="vertical-align:top;" headers="d235658e70-option" id="d235658e83">Client Secret</td>

            <td style="vertical-align:top;" headers="d235658e70-desc d235658e83">When a client registers with an OAuth2 provider, the provider issues the
              client a client secret, which is considered private and must be kept
              confidential. The value of this field is kept encrypted in the database (but is
              in plain text when exported from the database, or imported into the
              database).</td>

          </tr>
          <tr class="">
            <td style="vertical-align:top;" headers="d235658e70-option" id="d235658e92">Scopes</td>

            <td style="vertical-align:top;" headers="d235658e70-desc d235658e92">Corresponds to the scopes available for the OAuth2 provider and configured
              for the website when registering the website on the provider's website. The
              scopes are provider-specific and aren’t standardized. For more information, see
              section <a href="http://tools.ietf.org/html/rfc6749#section-3.3" target="_blank">3.3 Access Token
                Scope</a> in the OAuth2 specification.</td>

          </tr>
          <tr class="">
            <td style="vertical-align:top;" headers="d235658e70-option" id="d235658e105">Authorization URL</td>

            <td style="vertical-align:top;" headers="d235658e70-desc d235658e105">URL of the provider where the initial OAuth2 handshake occurs. For more
              information, see section <a href="http://tools.ietf.org/html/rfc6749#section-3.1" target="_blank">3.1 Authorization
                Endpoint</a> in the OAuth2 specification.</td>

          </tr>
          <tr class="">
            <td style="vertical-align:top;" headers="d235658e70-option" id="d235658e118">Token URL</td>

            <td style="vertical-align:top;" headers="d235658e70-desc d235658e118">URL of the provider where the token is requested from. For more
              information, see section <a href="http://tools.ietf.org/html/rfc6749#section-3.2" target="_blank">3.2 Token
                Endpoint</a> in the OAuth2 specification.</td>

          </tr>
          <tr class="">
            <td style="vertical-align:top;" headers="d235658e70-option" id="d235658e132">User Info URL</td>

            <td style="vertical-align:top;" headers="d235658e70-desc d235658e132">URL of the provider of the user information (first name, last name, email,
              and so on). For more information, see section <a href="http://tools.ietf.org/html/rfc6749#section-7" target="_blank">7
                Accessing Protected Resources</a> in the OAuth2 specification.</td>

          </tr>
          <tr class="">
            <td style="vertical-align:top;" headers="d235658e70-option" id="d235658e145">User Info URL Access Token Name</td>

            <td style="vertical-align:top;" headers="d235658e70-desc d235658e145">
              <p>Specifies the name of the query parameter.</p>
              <p>When a request to the User Info URL is made, the access token value is
                attached to the request as a URL query parameter value. This parameter value
                specifies the name of the query parameter. For most providers, it’s
                <code>access_token,</code> but it's different for some (for example,
                for LinkedIn, it’s <code>oauth2_access_token</code>).
              </p>
            </td>

          </tr>
          <tr class="">
            <td style="vertical-align:top;" headers="d235658e70-option" id="d235658e166">Redirect Pipeline Node</td>

            <td style="vertical-align:top;" headers="d235658e70-desc d235658e166">After the OAuth2 provider grants access to the client application, the
              provider returns control to the specified pipeline node.</td>

          </tr>
        </tbody></table>
4. To save your changes, click **Apply**.