{"errors":[{"message":"Could not authenticate you","code":32}]}

[digital_human]

Hi All,

I have the same issues as everybody here. Whatever i do, i keep getting Code 32. I checked my signature and it tells me its valid. Twitter still returns 32.

Signature base:

POST&https%3A%2F%2Fapi.twitter.com%2F1.1%2Fstatuses%2Fupdate.json&oauth_consumer_key%3Dk0xSiq29slKCdFlEDhvcsW6SA%26oauth_nonce%3D53a464e98191ccab830fe20fdc077488%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1463390947%26oauth_token%3D23585732-a785OuWKi9z30ENbBZaw5ydgCMUqrSCRUn2JF53C7%26oauth_version%3D1.0%26status%3DTest

Sign key:
MCD8BKwGdgPHvAuvgvz4EQpqDAtx89grbuNMRd7Eh98&IZ9Ywtove9OppIRXI4QPQDFBnU5MaJ36JoQCDfbws4oso

Signature: /jYdRlKkDPVMzbusnTRvI5ul5+E=

Array
(
[oauth_consumer_key] => k0xSiq29slKCdFlEDhvcsW6SA
[oauth_nonce] => 53a464e98191ccab830fe20fdc077488
[oauth_signature_method] => HMAC-SHA1
[oauth_timestamp] => 1463390947
[oauth_version] => 1.0
[oauth_token] => 23585732-a785OuWKi9z30ENbBZaw5ydgCMUqrSCRUn2JF53C7
[status] => Test
[user_secret] => IZ9Ywtove9OppIRXI4QPQDFBnU5MaJ36JoQCDfbws4oso
[oauth_signature] => /jYdRlKkDPVMzbusnTRvI5ul5+E=
)
Array
(
[0] => Authorization: OAuth oauth_consumer_key=“k0xSiq29slKCdFlEDhvcsW6SA”,oauth_nonce=“53a464e98191ccab830fe20fdc077488”,oauth_signature="%2FjYdRlKkDPVMzbusnTRvI5ul5%2BE%3D",oauth_signature_method=“HMAC-SHA1”,oauth_timestamp=“1463390947”,oauth_token=“23585732-a785OuWKi9z30ENbBZaw5ydgCMUqrSCRUn2JF53C7”,oauth_version=“1.0”
)
{“errors”:[{“code”:32,“message”:“Could not authenticate you.”}]}401{“errors”:[{“code”:32,“message”:“Could not authenticate you.”}]}

Remember: I regenerated the keys so you can’t use them. Hopefully you can help me fix this issue. I also checked with:https://dev.twitter.com/oauth/tools/signature-generator and my signature is correct. Still error code 32 returns.

Cheers,

Victor

[digital_human]

So finally I got it working. If you are sure your signature is correct and still get ERROR 32, this is because your request is not VALID. You can check this by:

$ch = curl_init();
curl_setopt($ch, CURLOPT_HTTPHEADER, $headers);
curl_setopt($ch, CURLOPT_HEADER, TRUE);
curl_setopt($ch, CURLOPT_URL, $this->status_url);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, TRUE);
curl_setopt($ch, CURLOPT_POSTFIELDS, “status={$parameters[“status”]}”);

    curl_setopt($ch, CURLINFO_HEADER_OUT, true);  //DEBUG METHOD TO GET SEND HEADERS

Send the request to Twitter: $result = curl_exec($ch);

Get the Send Request:

$status = curl_getinfo($ch, CURLINFO_HEADER_OUT); //DEBUG METHOD TO GET SEND HEADERS
echo “

”.print_r($status, true)."

";

Close it up: curl_close($ch);

If you need help. Send me Tweet on Twitter: @digital_human

[eastern_abdul]

I am on Android to integrate the Twitter API. why you guys of twitter does not provide well written documentation and snippet example for developers.
First the design of API is one of the bad one why does not provide mail on oauth authentication ?
Just close this useless APIs, don’t waste time.
I follow every step and still getting the same issue every time :@
{“errors”:[{“code”:32,“message”:“Could not authenticate you.”}]}
Meanwhile I am able to tweet from app but can’t get the verify mail address.
feeling exhausted

[andypiper]

Are you using Twitter Kit on Fabric?
https://docs.fabric.io/android/twitter/overview.html

We try to provide sample snippets in the Fabric documentation where we can.

[eastern_abdul]

I am using Twitter4J and ouath.

[eastern_abdul]

Basically I want to get the mail ID by whitelist the app.
https://dev.twitter.com/rest/reference/get/account/verify_credentials

[andypiper]

If you’ve raised a ticket to have you application key whitelisted for access to the email address, the team should get back to you shortly.

[eastern_abdul]

The problem is by using the twitter4j I am able to get the user profile information, and also able to tweet from android app but I cant get my mail ID, although my app is whitelisted. Can you give me some snippet to use this API to get the mail address?
https://dev.twitter.com/rest/reference/get/account/verify_credentials

[andypiper]

Twitter4J is a third-party library, so that’s why we don’t have examples that use it in our documentation directly.

Can you share the code you’re using? (without including any private data such as your app tokens)

Note that the parameter “true” to ?include_email must be specified as a string, not a boolean. You’ll also need to reauthenticate to Twitter in order to inherit the new permissions.

[eastern_abdul]

yes that all things are done. now one thing is remaining I am facing issue in generating the oath_signature param. I used the twitter generated params and that works fine but that is valid for few minutes. so I need some help regarding to generate the signature and all the steps so that I get rid of errors.
Thanks in advance

[eastern_abdul]

Here is the snippet
String toHash = URLEncoder.encode(“GET&https://” + “api.twitter.com/1.1/account/verify_credentials.json?include_email=true” + “&oauth_callback=oob&oauth_consumer_key=” + Constant.SHOWBOX_CONSUMER_KEY + “&oauth_nonce=” + unixTime + “&oauth_signature_method=HMAC-SHA1&oauth_timestamp=” + unixTime + “oauth_version=1.0”);

			String hash = computeHmac(toHash, Constant.SHOWBOX_CONSUMER_SECRET);

and here is method to generate the signtaure

public String computeHmac(String baseString, String key)
{
String result = “”;
try
{
Mac mac = Mac.getInstance(“HmacSHA1”);
SecretKeySpec secret = new SecretKeySpec(key.getBytes(), mac.getAlgorithm());
mac.init(secret);
byte[] digest = mac.doFinal(baseString.getBytes());
result = new String(Base64.encodeBase64(digest));
}
catch (Exception e)
{
e.printStackTrace();
}
return result;
}

[Stories360]

• I’ve created Fabric acc and used Fabric app to add TwitterKit in to my iOS app.
• OS app has linked whitelisted Twitter app with Consumer Key (API Key) & Consumer Secret (API Secret).
• I’ve regenerated Access Token and Access Token Secret.
• In .plist I changed, generated by FabricApp, Consumer Key (API Key) & Consumer Secret (API Secret) to the same from Twitter App account
• trying to login and get Could not authenticate you. (code 32)

[andypiper]

If this is a Twitter Kit question, can you ask on the relevant category here so the team can assist you? Thanks.

[Karthikeyan]

access token once got can’t be utilized after a few tries but this is not due to api rate limit rather it shows 401 unauthorized error code this problem if not solved is going to be a great discourage to devs so rectify soon or please tell us the root cause of this so that if we have any problem on our side we can rectify

[yellowSpasm]

Hello OAuth code:32 people. Just to share what was my mistake. I was trying to get request token in oauth/request_token step. Now, when generating oauth_signature we need to pass consumer SECRET (not consumer key as i did) as key(first argument) and signatureBaseString(second argument) to HMAC-SHA1 function. So once again HmacSha1 key is consumer secret percent encoded + “&”.

All mistakes a made were due to misinterpreting twitter docs or mysteriously substituting terms that different docs are mentioning. Some of errors I found were:

• nonce had 43 characters, when it should have 42 (not sure this is mistake but it didn’t followed docs )

• HMAC-SHA1 returned hex string, that cannot be fed to base64 encoding, you must use ArrayBuffer for exact binary maping of that string or simply write a function that converts that hex string to another non-hex string. Now this was due to mine own implementation of HMAC-SHA1 function, implementation that you use might do this already for you so check that also. Shameless reference to my implementation of Hmac.

• Oh, yes. I was worried that my SSL had something to do with code 32 error. When It did not. I’ve made ssl priivate key and cert by using OpenSSL command line tool, my cert was self signed my sever was node.js running on home pc. So you don’t have to have Certificate Authority signed cert to make request to twt api, at least for this 3-leg step authentication I was doing…

Now life can continue (to step 2 for now).

[DStratification]

For anyone who runs into something like this in the future, since I was pulling my hair out about this one.

If you are using a Python app to pass stuff to the API, this issue may not actually be related to your credentials at all. Per this thread, you need to make sure that you are using the ‘safe’ parameter. Failure to do so will result in “/” characters being encoded incorrectly, which will break OAuth authorization.

[MSerifios]

I finally did it!!!

In my case the problem was at the last step where i had my output from the hamc-sha1() and i was trying to base64 the output.

The output of the hmac-sha1 was like this 890148acbb265a53fd3479c75bb2d8866852f196
so when i was trying to convert into base64 this i was getting something like this ODkwMTQ4YWNiYjI2NWE1M2ZkMzQ3OWM3NWJiMmQ4ODY2ODUyZjE5Ng==.

That was something that put me in thoughts because at the twitter guide on how to make an oauth signature (bottom of the page) the author give as a much smaller output like hCtSmYh+iHYCEqBWrE7C7hYmtUk=

So i searched and find that the output of hmac-sha1 has to be interpreted as a hex before converted to base64

[abdulahad95]

This should be applied to all the forward slashes in the URL (the path parts) but not the forward slashes in ‘https://’ right? Because the quote function won’t work without a ‘http://’ or ‘https://’ in front. Just wanted to make sure I’m doing this right since I’m still getting the error and will look into my HMAC implementation now…
Thanks!

[andypiper]

[andypiper]