I'm having trouble determining what the "User Info Endpoint URL" should be when setting up a Auth Provider on a Salesforce org for LinkedIn.

I have correctly set up the Authorize Endpoint URL and the Token Endpoint URL for LinkedIn on Salesforce.. but I can't seem to find documentation anywhere for what the User Info Endpoint should be set to in Salesforce..

Any help would be greatly appreciated!


To clarify things, here is what I use for a Google Open ID Connect Auth Provider in Salesforce, as well as what I have so far for the LinkedIn one.

Authorize Endpoint URL https://accounts.google.com/o/oauth2/auth
Token Endpoint URL https://accounts.google.com/o/oauth2/token
User Info Endpoint URL https://www.googleapis.com/oauth2/v3/userinfo

Authorize Endpoint URL https://www.linkedin.com/uas/oauth2/authorization?scope=r_basicprofile%20r_emailaddress%20
Token Endpoint URL https://www.linkedin.com/uas/oauth2/accessToken
User Info Endpoint URL ?????????

  • Have you seen this documentation developer.linkedin.com/documents/profile-api?
    – Keith C
    Apr 29, 2014 at 22:08
  • Yes I have, still having issues getting the Auth Provider set up properly. Tried "api.linkedin.com/v1/people/~" and it was telling me invalid request. Apr 30, 2014 at 16:59
  • And are you including the access token in the request using this atypical parameter name developer.linkedin.com/forum/…?
    – Keith C
    Apr 30, 2014 at 17:08
  • I'm kind of confused as to which of those URLs I should be including that.. I edited my original question to show what I've been using for the URLs.. If I don't include an User Info Endpoint URL, it will take me to LinkedIn and ask me to login, then it takes me back to salesforce and in the URL gives me the following error: AuthorizationError?ErrorCode=No_Endpoint_URL&ErrorDescription=Could+not+generate+endpoint+URL Apr 30, 2014 at 17:45
  • If I add "linkedin.com/v1/people/~" as the User Info Endpoint URL in salesforce, it will take me to LinkedIn and ask me to login, then it takes me back to salesforce and in the URL gives me the following error: AuthorizationError?ErrorCode=Remote_Error&ErrorDescription=invalid_request Apr 30, 2014 at 17:47

1 Answer 1


I spent a little time trying to figure out how to get LinkedIn to work with the OpenID auth provider as well. While it does support OAuth2, it turns out that LinkedIn doesn't seem to support OpenID. On one of the webinars recently they mentioned that (Safe Harbor) LinkedIn Auth Provider might show up at the end of the year (similar to how Facebook has its own Auth Provider).

For now, you can use the Janrain Auth Provider (which can handle LinkedIn), or you can build it yourself.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .