LinkedInAdapter

Parse Server Configuration

To configure Parse Server for LinkedIn authentication, use the following structure:

Secure Configuration

{
  "auth": {
    "linkedin": {
      "clientId": "your-client-id",
      "clientSecret": "your-client-secret"
    }
  }
}

Insecure Configuration (Not Recommended)

{
  "auth": {
    "linkedin": {
      "enableInsecureAuth": true
    }
  }
}

The adapter requires the following authData fields:

• Secure Authentication: code, redirect_uri, and optionally is_mobile_sdk.
• Insecure Authentication (Not Recommended): id, access_token, and optionally is_mobile_sdk.

Auth Payloads

Secure Authentication Payload

{
  "linkedin": {
    "code": "lmn789opq012rst345uvw",
    "redirect_uri": "https://your-redirect-uri.com/callback",
    "is_mobile_sdk": true
  }
}

Insecure Authentication Payload (Not Recommended)

{
  "linkedin": {
    "id": "7654321",
    "access_token": "AQXNnd2hIT6z9bHFzZz2Kp1ghiMz_RtyuvwXYZ123abc",
    "is_mobile_sdk": true
  }
}

Notes

• Secure authentication exchanges the code and redirect_uri provided by the client for an access token using LinkedIn's OAuth API.
• Insecure authentication validates the user ID and access token directly, bypassing OAuth flows. This method is not recommended and may introduce security vulnerabilities.
• enableInsecureAuth is deprecated and may be removed in future versions.