Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>@sergionni I found answer to your Question from linkedin-developer</p> <p>As you know The first step to authorizing a Linked-In member is requesting a requestToken. This request is done with an HTTP POST.</p> <p>Your base string should end up looking something like this if you're using a callback:</p> <blockquote> <p>POST&amp;https%3A%2F%2Fapi.linkedin.com%2Fuas%2Foauth%2FrequestToken &amp;oauth_callback%3Dhttp%253A%252F%252Flocalhost%252Foauth_callback%26o auth_consumer_key%3DABCDEFGHIJKLMNOPQRSTUVWXYZ%26 oauth_nonce%3DoqwgSYFUD87MHmJJDv7bQqOF2EPnVus7Wkqj5duNByU%26 oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1259178158%26 oauth_version%3D1.0</p> </blockquote> <p>You then sign this base string with your consumer_secret, computing a signature. In this case, if your secret was 1234567890, the signature would be TLQXuUzM7omwDbtXimn6bLDvfF8=.</p> <p>Now you take the signature you generated, along with oauth_nonce, oauth_callback, oauth_signature_method, oauth_timestamp, oauth_consumer_key, and oauth_version and create an HTTP Authorization header. For this request, that HTTP header would look like:</p> <blockquote> <p>Authorization: OAuth oauth_nonce="oqwgSYFUD87MHmJJDv7bQqOF2EPnVus7Wkqj5duNByU", oauth_callback="http%3A%2F%2Flocalhost%2Foauth_callback", oauth_signature_method="HMAC-SHA1", oauth_timestamp="1259178158", oauth_consumer_key="ABCDEFGHIJKLMNOPQRSTUVWXYZ", oauth_signature="TLQXuUzM7omwDbtXimn6bLDvfF8=", oauth_version="1.0"</p> </blockquote> <p>Please note, that the HTTP header is a single header -- not an HTTP header for each component. You can optionally supply a realm="http://api.linkedin.com".</p> <p>As a response to your request for a requestToken, your requestToken will be in the "oauth_token" response field, a validation that we acknowledged your callback with the "oauth_callback_confirmed" field, an oauth_token_secret, and a oauth_expires_in, and a few other values.</p> <p>(here us Your answaer) response would look like:</p> <blockquote> <p>oauth_token=94ab03c4-ae2c-45e4-8732-0e6c4899db63 &amp;oauth_token_secret=be6ccb24-bf0a-4ea8-a4b1-0a70508e452b &amp;oauth_callback_confirmed=true&amp;oauth_expires_in=599</p> </blockquote>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload