"Failed to validate oauth signature and token" response


#1

I am getting following response for while trying to get request tokens for past two days. it used to work well before.

query :

https://query.yahooapis.com/v1/public/yql?q=SELECT%20*%20FROM%20twitter.oauth.requesttoken%20WHERE%20oauth_consumer_key="1LxkuaFQ82xXXXXXX0AND%20oauth_consumer_secret="1OsoXXXXXXuJAGjlcuArCwvPYY"%20AND%20oauth_callback="http://tweetoffline.appspot.com/Twitter-Authorize.html"&diagnostics=true&env=store://datatables.org/alltableswithkeys&format=json&callback=callbackrequesttoken&oauth_timestamp=1361394003&oauth_nonce=imzKsH&oauth_signature_method=HMAC-SHA1&oauth_version=1.0&oauth_callback=http://tweetoffline.appspot.com/Twitter-Authorize.html&oauth_signature=eRi1D88XXBnddkHcX0=

diagnostics:true
env:store://datatables.org/alltableswithkeys
format:json
callback:callbackrequesttoken
oauth_timestamp:1361394003
oauth_nonce:imzKsH
oauth_signature_method:HMAC-SHA1
oauth_version:1.0

oauth_signature:eRi1D88v6z0P3ovCylBnddkHcX0

response :
callbackrequesttoken({“query”:{“count”:1,“created”:“2013-02-20T21:00:04Z”,“lang”:“en-US”,“diagnostics”:{“publiclyCallable”:“true”,“url”:[{“execution-start-time”:“23”,“execution-stop-time”:“25”,“execution-time”:“2”,“proxy”:“DEFAULT”,“content”:“http://www.datatables.org/twitter/twitter.oauth.requesttoken.xml"},{“execution-start-time”:“30”,“execution-stop-time”:“32”,“execution-time”:“2”,“proxy”:“DEFAULT”,“content”:“http://www.datatables.org/oauth/oauth.utils.js”},{“execution-start-time”:“32”,“execution-stop-time”:“36”,“execution-time”:“4”,“proxy”:“DEFAULT”,“content”:“http://oauth.googlecode.com/svn/code/javascript/oauth.js”},{“execution-start-time”:“38”,“execution-stop-time”:“42”,“execution-time”:“4”,“proxy”:“DEFAULT”,“content”:“http://oauth.googlecode.com/svn/code/javascript/sha1.js”},{“execution-start-time”:“59”,“execution-stop-time”:“154”,“execution-time”:“95”,“http-status-code”:“401”,“http-status-message”:“Unauthorized”,“proxy”:“DEFAULT”,“content”:“http://twitter.com/oauth/request_token?oauth_callback=http%3A%2F%2Ftweetoffline.appspot.com%2FTwitter-Authorize.html”}],“cache”:[{“execution-start-time”:“27”,“execution-stop-time”:“28”,“execution-time”:“1”,“method”:“GET”,“type”:“MEMCACHED”,“content”:“b8ebdfdf96993b874df1826af5063586”},{“execution-start-time”:“28”,“execution-stop-time”:“29”,“execution-time”:“1”,“method”:“GET”,“type”:“MEMCACHED”,“content”:“14.99.80.252”}],“redirect”:{“from”:“http://twitter.com/oauth/request_token?oauth_callback=http%3A%2F%2Ftweetoffline.appspot.com%2FTwitter-Authorize.html”,“status”:“301”,“content”:“https://twitter.com/oauth/request_token?oauth_callback=http%3A%2F%2Ftweetoffline.appspot.com%2FTwitter-Authorize.html”},“javascript”:{“execution-time”:“125”,“instructions-used”:“845880”,“table-name”:“twitter.oauth.requesttoken”},“user-time”:“154”,“service-time”:“109”,“build-version”:“33944”},“results”:{“result”:"Failed to validate oauth signature and token\n”}}});


#2

You should use the API directly. Proxying your credentials through a third party is not a good idea. Be careful that you don’t post your keys in a public forum. Make sure you’re using up to date paths – https://api.twitter.com/oauth/* instead of https://twitter.com/oauth/*

Keep in mind that API v1 is being retired and that you should upgrade to 1.1 if you haven’t already.