Linkedin Api The remote server returned an error: (401) Unauthorized

Question

I am working on the Linkedin Api. In my OAuthLinkedin.cs, I have the following:

        public string WebResponseGet(HttpWebRequest webRequest)
        {
            StreamReader responseReader = null;
            string responseData = "";

            try
            {
                responseReader = new StreamReader(webRequest.GetResponse().GetResponseStream());
                responseData = responseReader.ReadToEnd();
            }
            catch
            {
                throw;
            }
            finally
            {
                webRequest.GetResponse().GetResponseStream().Close();
                responseReader.Close();
                responseReader = null;
            }

            return responseData

; } My code is able to get a oauthToken, oauthTokenSecret

WebResponseGet(HttpWebRequest webRequest) is where it fails. Status: System.Net.WebExceptionStatus.Protocol error The remote server returned an error: (401) Unauthorized.

It is able to get a token secret after requesting permission to access linkedin. but I am not sure abt this unauthorized error. is it some permission issue. where do I check this

Thanks Sun

hopefully you anonymized your token secrets in this post ;-) — kroonwijk
– kroonwijk, Commented Sep 26, 2011 at 21:42

Johnny Oshika · Accepted Answer · 2011-10-29 06:04:47Z

2

Here are a couple of things that you can try to identify the source of your problem:

Use this OAuth test console and compare the header that you're generating to the one that this tool generates: https://developer.linkedin.com/oauth-test-console If your header is wrong, then LinkedIn will return a 401 status
If you're posting XML to LinkedIn in your request, then make sure the content type (webRequest.ContentType) is "application/xml" and not "application/x-www-form-urlencoded", otherwise, LinkedIn will return a 401 status.

answered Oct 29, 2011 at 6:04

Johnny Oshika

58k41 gold badges197 silver badges286 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Syed Shariq · Accepted Answer · 2013-01-09 03:39:11Z

0

It was happening with me too but i figured it out what i was doing it wrong.

Whenever you create Signature, make Token and TokenSecret empty. it worked for me because it was getting old token and token secret from browser request.

 //Generate Signature
        string sig = this.GenerateSignature(uri,
            this.ConsumerKey,
            this.ConsumerSecret,
            this.Token,
            this.TokenSecret,
            method.ToString(),
            timeStamp,
            nonce,
            out outUrl,
            out querystring);

answered Jan 9, 2013 at 3:39

Syed Shariq

92 bronze badges

Collectives™ on Stack Overflow

Linkedin Api The remote server returned an error: (401) Unauthorized

2 Answers 2

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related