(215) Bad Authentication data

BancodeSeries · 2014-09-25T19:08:59.246Z

actually I just checked I don’t update twitteroauth for a while. Will try the latest version and see if works

kfenger · 2014-09-25T19:13:13.536Z

BancodeSeries:

Any specific change on twitteroauth.php that could fix the problem for people using the php module?

We use our own Curl library, but at a quick glance here, it looks like twitteroauth uses the same oauth library. So, changing the following line (no guarantees this won’t break other POST requests going through here may want to add a couple other checks, strpos on statuses/update or something) to use the oauth function to_url() instead of get_normalized_http_url, will likely be a nice workaround for the time being.

183: default:
return $this->http($request->get_normalized_http_url(), $method, $request->to_postdata());

to this

183: default:
return $this->http($request->to_url(), $method, $request->to_postdata());

also like to add, that this is hacky, and only is going to be a workaround…

benjaminnimmo · 2014-09-25T19:13:30.477Z

In twitteroauth.php you can update the http function with this around line 232

switch ($method) {
  case 'POST':
    curl_setopt($ci, CURLOPT_POST, TRUE);
    if ($authorization_header)
      $headers[] = $authorization_header;
    if (!empty($postfields)) {
      curl_setopt($ci, CURLOPT_POSTFIELDS, $postfields);
    }
    if(!$authorization_header) $url = $url.'?'.$postfields;
    break;
  case 'DELETE':
    curl_setopt($ci, CURLOPT_CUSTOMREQUEST, 'DELETE');
    if (!empty($postfields)) {
      $url = "{$url}?{$postfields}";
    }
}

It works but it’s a horrible fix.

BancodeSeries · 2014-09-25T19:22:34.583Z

kfenger:

183: default: return $this->http($request->get_normalized_http_url(), $method, $request->to_postdata());

to this

183: default: return $this->http($request->to_url(), $method, $request->to_postdata());

also like to add, that this is hacky, and only is going to be a workaround…

This change worked. Thanks!
But, what is happening now is a feature or a bug??

elquijote1605 · 2014-09-25T19:23:11.475Z

I’m getting a 215 Bad Authentication Data from two hours ago. I can’t use statuses.update but have no problem with another API, like statuses.home_timeline. Does anybody knows what’s happening? I’m using the twitter package for python.

kfenger · 2014-09-25T19:34:05.496Z

elquijote1605:

I’m getting a 215 Bad Authentication Data from two hours ago. I can’t use statuses.update but have no problem with another API, like statuses.home_timeline. Does anybody knows what’s happening? I’m using the twitter package for python.

statuses.home_timeline is a GET request. The GET requests includes the oauth information in the url_parameters.

statuses.update is a POST request. The POST requests in most libraries will include the oauth information in the POSTFIELDS. The problem is that Twitter is not accepting/grabbing the information in the POSTFIELDS.

This means that GET requests will work fine, since everything is sent in the url. That’s why the workarounds above work is because we include what we normally put in POSTFIELDS in the url_parameters.

diegoteixeir4 · 2014-09-25T19:36:28.403Z

Is it a change or an issue?

benjaminnimmo · 2014-09-25T20:15:55.206Z

diegoteixeir4:

Is it a change or an issue?

this is the big question?

benfisher · 2014-09-25T20:24:47.521Z

In my opinion, big issue! Doubt it’s intentional - is there another venue we can report defects to?

elquijote1605 · 2014-09-25T20:34:56.815Z

The question for me is if it’s a problem Twitter will fix soon or later or do I have to rewrite all code based in statuses/update.

chaselee · 2014-09-25T20:39:01.369Z

Seeing the same problem.

NeoDev · 2014-09-25T20:43:45.983Z

My app is having the same problem publishing statues.

We are using twitteroauth library:

183: default:
return $this->http($request->get_normalized_http_url(), $method, $request->to_postdata());

to this

183: default:
return $this->http($request->to_url(), $method, $request->to_postdata());

This solved the problem temporarily.

Any official words from twitter?

compston · 2014-09-25T21:13:07.576Z

Sorry for the delay everyone. We’re currently working to roll back a change that is causing this behavior. I’ll follow up when that process is complete, but it should resolve the issue for you.

gmbradley · 2014-09-25T21:49:57.566Z

Instead of 215 ‘Bad Authentication data’ I’m now seeing a ton of 32 ‘Could not authenticate you’ errors instead. Anyone else?

Twitaculous · 2014-09-25T21:58:33.495Z

Probably a bit superfluous as @compston says it’s being fixed but many of my members have been experiencing it today

NeoDev · 2014-09-25T21:59:35.770Z

I concur.

compston · 2014-09-25T22:33:58.058Z

Could you 1) confirm that you’re still getting the new code 32 error, and 2) if so, paste in the full HTTP request / response?

NeoDev · 2014-09-25T22:41:29.909Z

Here’s mine:

https://api.twitter.com/1.1/statuses/update.json?oauth_consumer_key=xxxxxx&oauth_nonce=xxxxx&oauth_signature=xxxxx&oauth_signature_method=HMAC-SHA1&oauth_timestamp=xxxxx&oauth_token=xxxxx&oauth_version=1.0&status=Testing%20twitter%20publish%20from%20sandbox

Response:

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

Edit: nevermind, restoring the temporary fix would resolve the problem.

diegoteixeir4 · 2014-09-25T22:45:22.999Z

i got the same error (32). You need to put the data in the POSTFIELDS. It worked for me.

kfenger · 2014-09-25T22:46:26.187Z

compston:

Could you 1) confirm that you’re still getting the new code 32 error, and 2) if so, paste in the full HTTP request / response?

Working here.