Failed to validate oauth signature and token

Marlex · 2011-12-13T05:35:46.000Z

Hello,

I’ve tried in so many ways this thing to “sign” the request… And I don’t understand what I’m doing wrong…

I’m trying to post https://api.twitter.com/oauth/request_token with this Authorization header:

OAuth oauth_nonce=“pkZgsQSnLFxrW8MhbUH7419vyuNZnI0zTvKBWRf5Az”, oauth_callback=“oob”, oauth_consumer_key=“HIDDEN”, oauth_signature=“YmZkNjhlMzhlMmM2NjI2YWY5ZjcyYThkNGE2YTMyYzNmMzdmZDhlYg%3D%3D”, oauth_signature_method=“HMAC-SHA1”, oauth_timestamp=“1971754813”, oauth_version=“1.0”



Any help would be appreciated...

PS: Even my computer and my webserver has the right timezone and time. I've checked twice even visiting http://www.unixtimestamp.com/index.php to being sure that the timestamp showing up is, indeed, right.

kurrik · 2011-12-13T16:59:15.000Z

The signature doesn’t look like a valid signature to me. Are you using a library to perform the signing?

Marlex · 2011-12-14T03:30:29.000Z

@kurrik, I’m using Javascript with a library made by me. I found the problem. The parameters must be ordered alphabetically before send it to Twitter API… I was sending those parameters with a random order so I assume is that because when I ordered, it works.

My fault, that happened when you forgot to read. You know, RTFM!

kurrik · 2011-12-14T22:23:10.000Z

I’m glad to hear you figured it out

Susan431 · 2011-12-14T22:31:50.000Z

Thank you

venkatkorampall · 2013-03-15T11:50:00.000Z

Hi,

I am consuming the twitter API using a library. When i am trying to get the request token using the url https://twitter.com/oauth/request_token it is returning as “Failed to validate oauth signature and token”

Can any one help me in resolving this issue?

episod · 2013-03-15T14:05:50.000Z

Many good tips here: [node:204]. One tip, use the right path: https://api.twitter.com/oauth/request_token

ClinicMattersTV · 2013-06-16T21:20:43.000Z

it took less than 30 mins to get my app using google’s youtube api. it’s 5hrs and am still on ur API 's oAuth. i wonder what to expect when am finally able to fix the “Failed to validate oauth signature and token” error.

ClinicMattersTV · 2013-06-16T21:53:10.000Z

if time is wrong, you get "Failed to validate oauth signature and token"
if you supply no param, same error. fixing it is better than dozen tips.

sphinx1410 · 2013-07-05T09:07:21.000Z

I have met the same problem, here is the header:
OAuth oauth_nonce=“glxomnct08x0gfialw”, oauth_callback=“http%3A%2F%2Fwww.baidu.com”, oauth_signature_method=“HMAC-SHA1”, oauth_timestamp=“1373014401”, oauth_consumer_key=“9BFD1XOiVFHrnS7Hw78yA”, oauth_signature=“Qm2WJtOMYAJ8FpOfBAar5THKbdo%3D”, oauth_version=“1.0”

nearly the same as the sample in https://dev.twitter.com/docs/api/1/post/oauth/request_token

OAuth oauth_nonce=“K7ny27JTpKVsTgdyLdDfmQQWVLERj2zAK5BslRsqyw”, oauth_callback=“http%3A%2F%2Fmyapp.com%3A3005%2Ftwitter%2Fprocess_callback”, oauth_signature_method=“HMAC-SHA1”, oauth_timestamp=“1300228849”, oauth_consumer_key=“OqEqJeafRSF11jBMStrZz”, oauth_signature=“Pc%2BMLdv028fxCErFyi8KXFM%2BddU%3D”, oauth_version=“1.0”

Do you have any idea of it? BTW, how to post a new topic on Discussions?

NanelTai · 2013-09-06T17:22:31.000Z

how found the oauth_signature, I do not understand how to make them or the SHA1 encrypted embedded parameters

JRedded · 2013-12-11T23:45:36.000Z

IN PHP:

$signature = base64_encode(hash_hmac(“sha1”, $sigstring, $sigkey, TRUE))

That TRUE was important as it outputs the required raw binary, rather than the default output of hexbits.

Fatifratt · 2013-12-12T00:27:52.000Z

I can’t validate when asked. I used to be able to. I use an iPad.

vis_1321 · 2014-02-03T07:15:39.000Z

Hi,
I have been using scribe lib for authentication process .Everything was working fine ,but since last week I’m getting problem in the request_token ,the error which I get is “Failed to validate oauth signature and token”

Please help me to figure it out what may be the issuses,I have changed and checked my timezone which is correct,still getting same error.

thanks.

azamalvi · 2014-07-30T19:50:03.000Z

I figured it out and found the solution.
It is due to session. When we first send call to twitter and we login form twitter then it sets the session variables. After same time we again login then this error comes. Solution is only destroy the session then again do that this time error will not come.

Hope this will help