Set Up Connectors with LinkedIn OAuth

To create a connection in Data Cloud securely without sharing passwords, some external connectors allow access using OAuth (Open Authorization). If using LinkedIn OAuth, there are several prerequisite implementation steps to complete before you connect the source to Data Cloud.

Required Editions

Available in: All Editions supported by Data 360. See Data 360 edition availability.

Follow these prerequisite steps before connecting to the data source in Data Cloud Setup. To complete these steps you must have admin access.

Bookmark this page or keep it open to refer to this topic as you complete these tasks.

Note Steps and links outside of Salesforce content may not be updated or accurate.

Create a Custom OAuth Application

Before you can define your authentication provider in Salesforce, you can optionally create a custom OAuth application on your provider's website. The process can vary depending on your provider.

1. Create a private app according to LinkedIn's documentation.
2. Write down these configuration values:
   1. Client ID
   2. Client Secret
   3. Authorization Endpoint URL (optional)
   4. Token Enpoint URL (optional)

Configure an Authentication Provider

Create an authentication provider in Salesforce and then update your provider with the callback URL.

1. From Setup, in the Quick Find box, enter Auth. Providers, and then select it.
2. Click New and select LinkedIn from the provider type dropdown.
3. Fill out the required information.
   1. Name—Enter a name for the Authentication provider.
   2. URL Suffix—The URL automatically gets suffixxed with the name you have given to the Authentication provider.
   3. Consumer Key—Add the Client ID from LinkedIn.
   4. Consumer Secret—Add LinkedIn's Client Secret Value.
4. Click Save.

Several client configuration URLs are generated after defining the authentication provider. Write down the callback URL from the Salesforce configuration after you save your work.

After defining the authentication provider in Salesforce, go back to your provider and update your app's callback URL.