Troubleshooting OAuth 1.0A

criacon · 2012-05-17T05:44:31.000Z

thanks for you information

rivan_ipai · 2012-05-18T04:08:48.000Z

please help me… how to get permission xauth for my application??i create my application for my thesis… please help me…

DeepikaLalra · 2012-08-03T11:52:00.000Z

Yes It worked for me.

Thanks

Mayank3872 · 2012-08-07T06:43:33.000Z

I created twitter application ,when click on Authenticate user ,always get Oauth_token null.Please help me

ChadCorbitt · 2012-08-20T19:23:11.000Z

Hey it looks like my API has been soft blacklisted. How do I go about correcting this or discovering why this happened? Any help would be greatly appreciated.

episod · 2012-08-20T19:53:12.000Z

If you suspect this to be the case (what signals are you reading?), consult this FAQ entry for next steps:
[faq:5820]

dZkF9RWJT6wN8ux · 2012-08-22T13:17:00.000Z

I encounter the same problems as you. I can’t use the OAuth tool for getting a Request Token, by calling the URL specified at https://dev.twitter.com/docs/api/1/post/oauth/request_token.

I’m also trying to build my own Twitter API in C++ and I get the following error “Failed to validate oauth signature and token” when I try to make an HTTP GET request with the oauth_* parameters in the query string to https://api.twitter.com/oauth/request_token.

Here is my base signature string:
GET&https%3A%2F%2Fapi.twitter.com%2Foauth%2Frequest_token&oauth_callback%3Dhttp%3A%2F%2Fwww.google.com%26oauth_consumer_key%3DB4TLzqGFHCMyHcBEsQnhQ%26oauth_nonce%3D134563948633%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1345639486%26oauth_version%3D1.0

And I make a GET request to the following URL after the oauth_signature is generated:
https://api.twitter.com/oauth/request_token?oauth_callback=http%3A%2F%2Fwww.google.com&oauth_consumer_key=B4TLzqGFHCMyHcBEsQnhQ&oauth_nonce=134563948633&oauth_signature=vhczF1AhtAphlAzw333kQiJquAE%3D&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1345639486&oauth_version=1.0

After following some of the troubleshooting tips at the top of this page and debugging my oauth_* params value generation code I can’t find where the problem is I still get “Failed to validate oauth signature and token” and “401 Unauthorized” HTTP response code. and reason phrase.

Have you found a solution for making HTTP requests from the OAuth tool to the URL https://api.twitter.com/oauth/request_token that return “200 OK” and a valid request token?

episod · 2012-08-22T14:50:13.000Z

The OAuth tool isn’t capable of generating sample requests to oauth/request_token as the OAuth tool is for accessing API resource methods while utilizing a user context. oauth/request_token has no user context and you can’t include an oauth_token as part of the request.

I encourage you to utilize Authorization-header based OAuth instead of querystring; querystring can complicate your encoding quite a bit.

By passing a URL-escaped URL on the query string, you are required to escape the value again in the signature basestring. (As above, so below).

dZkF9RWJT6wN8ux · 2012-10-07T22:45:23.000Z

My issue was as follows:

I’ve done an base64 encoding to the strDigest received from the HMAC-SHA1 algorithm, as described by section 3.4.2 of RFC 5849, https://tools.ietf.org/html/rfc5849#section-3.4.2:
string base64Str = base64_encode(strDigest);

But I also did an URL encoding to the base64Str by mistake, which was the second problem. This is what I did wrong, i.e.URL encoded the base64 string:
oAuthSignature = UrlEncode(base64Str);

Removing the line above and replacing it with “OAuthSignature = base64Str;” solved my problem with doing an HTTP GET request by passing the oauth_* parameters by query string.

For now I can’t use:

The HTTP “Authorization” header field
nor
The HTTP request entity-body
Because my HTTP client doesn’t allow me to provide headers for the HTTP request, I can only see the HTTP response headers.

I hope the less preferred method - the HTTP request URI query - will work for my use cases, at least for the moment.

Thanks for the help.

Itz_LeeO · 2012-09-20T18:06:27.000Z

I am developing an application for Java ME devices. I have the correct tokens/secrets, and I have a method for accurately generating signatures. I created the request headers using the setRequestProperty(String key, String value) method in the javax.microedition.io.HttpsConnection interface but when I try to perform an API call (like retrieving home_timeline.json), I get a HTTP 401 error with error code 135.
I tried adjusting my oauth_timestamps, but I still get the same error, only now the error code is 32.
I’ve tried everything but nothing changes.
Can someone help me out here???

BrandonFuller · 2012-10-16T22:10:35.000Z

My app broke when I had to migrate from Twitter API 1.0 to 1.1. Ended up finding out that I was missing this header in my POSTs:

Content-Type: application/x-www-form-urlencoded

ACDTesting1 · 2012-11-06T22:49:00.000Z

Ok, I am able to execute the statuses/home_timeline GET request with my current IDs and tokens, so I know they are correct and I know that I am able to create the correct OAuth signature. Having said that, I am attempting to update my Twitter status and I am getting an “Could not authenticate you” error. I’m building this little app with ColdFusion and this is my code for the call:

Status = “This%20is%20a%20test%20tweet”

I tried including all the oauth variables as header elements in the cfhttp, no go. I tried the status param as a type “body”, no go. I’m still getting the same authentication error, yet I know the above oauth variables work because if they didn’t, I would not be able to grab the home_timeline which I can. Can anybody help me figure out why I’m still getting this “Could not authenticate you” error?

episod · 2012-11-07T16:02:20.000Z

Performing HTTP GETs in OAuth is a bit different than POSTs. I would verify that the underlying OAuth code you’re using is generating the signature base string correctly. I would make sure that when you send status with spaces as %20, that your HTTP and OAuth code are in coordination and not overly zealous about re-encoding it again.

ACDTesting1 · 2012-11-07T23:04:00.000Z

I just redid my tokens, did a GET successfully, did a POST unsuccessfully (same error). This is my signature base string that was created during my one attempt:

POST&https%3A%2F%2Fapi.twitter.com%2F1.1%2Fstatuses%2Fupdate.json&oauth_consumer_key%3D***CONSUMERKEY***%26oauth_nonce%3Dzed5ro2mwe9lc58aqd7zjen0sr7cxlp3%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1352328864%26oauth_token%3D***ACCESS_TOKEN%26oauth_version%3D1.0%26status%3DThis%2520is%2520a%2520test%2520tweet

Now I am assuming that the signature is generated correctly, because if it wasn’t, I would not have been able to execute the GET successfully (it uses the same function and encoding mechanism). Is there something wrong in the base string?

episod · 2012-11-08T14:59:00.000Z

How are you constructing your POST? Does it send the proper Content-Type and Content-Length headers that a POST should? Are you able to examine the request in transit and verify that your POST parameters are being sent correctly?

ACDTesting1 · 2012-11-08T18:25:00.000Z

I can’t recall if I sent you this response, but if I did again, I apologize.

Here’s how I’m constructing my POST:

    </cfhttp>

I’m not getting a throw on error, but I am returning a 401 Unauthorized error in the HTTP header response of mimetype application/json. I don’t know what I need to consider in the content-length - just the status message I’m trying to update? I tried that, and I tried type “url” instead of “formfield” for the status message but to no avail. I’m honestly lost on where I need to go from here.

episod · 2012-11-09T15:53:50.000Z

I’m more interested in how ColdFusion is performing the POST – you could be telling it to do everything right as far as you know and it still could be doing something wrong. I’m not very familiar with this style of coding and it seems like a very brittle & indirect way to go about interacting with the API.

ACDTesting1 · 2012-11-16T15:31:00.000Z

I figured out the issue. The status cfhttpparam needs to be of type=“body” and the value is the URL-encoded query string of the data:

episod · 2012-11-16T15:47:05.000Z

Glad to hear you figured this out!

avantajtvm1 · 2012-11-20T06:50:20.000Z

I have downloaded the latest api of twitter from git. When i login using the credentials of my twitter account. I am being redirected to my twitter homepage instead of redirecting to my return url.This is the Link