
To prevent others from reading your requests and to prevent man-in-the-middle attacks, all OAuth 2.0 requests to our authentication servers must be done over HTTPS. Make sure you do not expose this request publicly! Secure APIs
Make linked javascript file secure code#
Remember that when exchanging an OAuth 2.0 authorization code for an access token, client_secret is passed as part of the request.

Do not expose files such as JavaScript or HTML files in client-side code.When creating a native mobile application, do not store it locally on a mobile device.Do not share your access tokens with anyone, and do not pass it in the URL when making API calls, or URI query-string parameters, or post in support forums, chat, etc.Follow these suggestions to keep the secret safe:

The Client Secret is confidential and should only be used to authenticate your application and make requests to LinkedIn's APIs.īoth the Client ID and Client Secret are needed to confirm your application’s identity and it is critical that you do not expose your Client Secret. The Client ID is a public identifier of your application. Two pieces of identifiable information are required to make calls to the LinkedIn API: Client ID (Consumer Key/API key) and Client Secret.
