API 1.1 PHP Inconsistent Authentication?

cr8ivecodesmith · 2012-09-15T10:42:43.000Z

Hi! I think this problem may be somewhat related with this discussion: https://dev.twitter.com/discussions/10693

However I’m trying API 1.1 on (Cake)PHP.

I seem to authenticate just fine on ‘/1.1/account/verify_credentials.json’ while supplying my oauth_consumer_key, oauth_consumer_secret, oauth_token, and oauth_token_secret over ‘GET’ method.

Now when I try to call ‘/1.1/users/search.json’ and supplying the same oauth parameters and same ‘GET’ method, It returns with a message:
‘Could not authenticate you’ code 32.
I even tried ‘POST’ method and it’s still the same error.

I’ve been searching and trying out things to no avail. I’m hitting a wall with this already. What am I missing out?

episod · 2012-09-17T15:12:33.000Z

In this case, it’s likely something around parameter encoding in your signature base string. Do you know how you’re building your signature base string when considering parameters like your “q” value in users/search?

sergeykalin · 2012-09-24T10:48:40.000Z

Maybe it helps:
I faced a problem alike in Java. I used Apache URLEncoder to encode my parameters and all worked fine at API v1, but with v1.1 it hit a problem when * (star) character present in parameter values. I’m pretty sure that there are other character that could hit the issue. Spend a half of day to locate a problem.

And found following. When you calculate your base string you are to encode * to %2A. It could be confirmed with Twitter OAuth tool. In my case * was not encoded in POST body while was encoded at base string. API v1 worked with it, but v1.1 is not.

It seems tricky and special characters processing could vary between implementations of URL-encoding, especially in case what characters to encode. You could check RFC3986 for more details http://www.ietf.org/rfc/rfc3986.txt

winterstein · 2013-03-13T11:07:50.000Z

Thanks @sergeykaliln – your post helped me!
I also use Java, but with the native java.net.URLEncoder. That has 2 & only 2 issues:

which you need to encode as %2A,
and space, which gets encoded to +, but Twitter needs %20

E.g. use

String value;
String encoded = URLEncoder.encode(value, “UTF-8”)
.replace("*","%2A").replace("+","%20");

Everything else (other ascii chars & unicode) works fine.

ifynk · 2013-06-12T13:17:00.000Z

Please, help! What is wrong with my query?
{“errors”:[{“message”:“Could not authenticate you”,“code”:32}]}

https://api.twitter.com/1.1/users/show.json?user_id=128156112

Authorization: OAuth oauth_token=“66666-heh3K4vkiWWhTtRBi4WWMo9n5voca9ietxruq19I”, oauth_consumer_key=“3uFaWjfStmB0y6aWYvJl8j4ANcsaRW7cseWExWecrXU”, oauth_version=“1.0”, oauth_timestamp=“1371042751”, oauth_nonce=“8avAJJCS53JJsKjmROZhCR3XlBllRIQ4Wsacxftc”, oauth_signature_method=“HMAC-SHA1”, oauth_signature=“dzc%2BAr0G0HH4yquE%2F11vUALLX0Q%3D”

episod · 2013-06-12T14:38:11.000Z

Take a look at [node:204] for tips on debugging OAuth problems.

ifynk · 2013-06-13T11:25:52.000Z

I tried. but its not helped (

stefangaemperle · 2013-06-14T07:03:22.000Z

got the same problem

ifynk · 2013-06-14T08:29:29.000Z

Please. I checked all of parameters - signature base string is true. used rawurlencode/decode for params. On v1 all worked early, but now v1.1 not worked. Help me.