Access Token for LinkedIn

Configure an access token to connect to LinkedIn.

Figure: LinkedIn Access Token Configuration screen

LinkedIn Access Token Configuration screen

Background and Setup

Prerequisites

Good to Know

Fields

Field Name Definition

Token Name

Function:
Specifies the unique name for your connection to LinkedIn service.
Accepted Values:
A text string that can have letters, numbers, and spaces.
Default Value:
None

Client ID

Function:
Specifies the client ID for your LinkedIn service.
Accepted Values:
A string with letters and numbers.
Default Value:
None

Client Secret ID

Function:
Specifies the client secret ID for your LinkedIn service.
Accepted Values:
A string with letters and numbers.
Default Value:
None

Redirect URL

Function:
Specifies the callback URL from the connected application.
Accepted Values:
A string in URL format.

Description

Function:
A description for your access token.
Accepted Values:
More than one line of text.
Default Value:
None
Example:
Refer to:

OAuth2 Access Token

Function:
Specifies an access token, or code, from LinkedIn.
Accepted Values:
A valid access token

This value comes from LinkedIn.

Default Value:
An unique access token.

Get OAuth2 Access Token

Function:
Sends a request to the LinkedIn service to get the access token.

To complete this process, you must sign in to LinkedIn, and specify your consent when prompted.

Encrypt

Function:
Stores the access token in the AgilePoint database as encrypted data.
Note: AgilePoint recommends you to store this access token in the database in encrypted format.
Accepted Values:
  • Deselected - The access token is in plain text in the database.
  • Selected - The access token is encrypted in the database.
Default Value:
Selected
Limitations:
  • This field was removed from the UI in AgilePoint NX OnPremises and PrivateCloud v7.0 Software Update 2. Access token credentials are encrypted by default. If you want to store credentials in unencrypted format, contact AgilePoint Customer Support.