"401 Not Authorized" in API OAuth PHP authorization

[@matheuseduardo]

I have tested the api twitter with at least four solutions (one of them everworked before, months ago) in PHP, and getting the same error: "401 Not Authorized".

Is there any "novelty", any prior authorization to be given to theapplication?

There are others with the same problem?

Someone trying anything new in PHP and working well?

[Scott Wilcox]

Checked your tokens are correct?

[@matheuseduardo]

Yep! And try to reset keys, delete application, create other, create other in other user... and nothing worked as well!

I've downloaded some ready for test examples from github, from posts.. nothing.

Even the popular "@abraham's Twitter OAuth library for PHP" (which was just change the two keys and worked in past) did not work here! and have the same error "401 Not Authorized" in header (instead 200 Ok).

There is someone trying "something new" in PHP with Oauth, that can send me the sample files so I just enter my keys and test?

Rgds

(sorry for bad english, with the help of google translator)

[Ninjamonk]

I am having the same issue, code that worked yesterday is now throwing
401's - I am using .net

[Ninjamonk]

it seems to be back and working fine now.

[@matheuseduardo]

My problem persist and I still receiving a "Failed to validate oauth signature and token".

But in all examples is well signed with "HMAC-SHA1" as suposed to be.

I can't get the "request token" therefore I can't get the "authenticate url" (to access twitter authentication page, etc).

Someone can help?

[@matheuseduardo]

Anyone using PHP having this same problem?

Anyone with sample working code to send me?

Even using https://github.com/abraham/twitteroauth ?

[Scott Wilcox]

Check the time is accurate on the machine you're running the code on.

[@matheuseduardo]

seems to be ok
the function that generate the is just:

function generate_timestamp() {
   return time();
}

and in header I have the parameter: [oauth_timestamp] => 1300471769

the error received from request in twitter api is: "Failed to validate oauth signature and token" and header 401

Must be signature?

I just think it's weird because it's happening in all library and examples ready for tests..

[Matt Harris]

Hi,

The error message "Failed to validate oauth signature and token" does mean either the signature you are sending, or the consumer token is invalid. Could you share the request you are making, and response you are getting. Remember to obscure any user or consumer secrets.

Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris

--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: http://groups.google.com/group/twitter-development-talk

[@matheuseduardo]

just a question: for request, the time need to be GMT 0?

[@matheuseduardo]

I'm doing another try.. and this time I trying with "Wootter" that is a twitter opensource "client".

Then I've downloaded and just change the keys in config.php. In Demo server is right working... but in my server, not.

I just don't know why can't get authenticate url through request that is responding with 401 header.

[devjyoti patra]

Hi,

My Streaming APi code has suddenly started to throw 401 (UNAUTHORIZED) message. It was working properly till yesterday and hence I'm sure that my credentials are okay. This is what I'm catching after sending my oAuth tokens.

Error 401
Problem accessing /1/statuses/filter.json. Reason: UNAUTHORIZED

Thanks,
Devjyoti

--