Has OAuth changed today 9/25?


#1

Our applications all use OAuth to post status updates and have been working fine until about 2:30PM EST today. Now our applications all return an error 215 (bad auth)???


#2

Have exactly the same problem here, so it’s something their end, and not ours.


#3

Our application started to get error 32 “Could not authenticate you”. We’re using API v1.1. It was working for months before without changes.


#4

sorry, forgot to mention version we’re using 1.1 also


#5

#6

We are having same issue. I think something got changed in Twitter OAuth. Does anybody has any solution yet?


#7

It appears as though the Twitter API is no longer supporting oauth parameters in the URL or body. But, putting them in the Authorization header made the requests go through.


#8

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.


#9

Thank you for your patience. This issue should be resolved. Please visit the OAuth section of the forum for further support. For any further inquiries regarding OAuth please open a new thread in the OAuth category https://twittercommunity.com/category/oauth

Thanks!


#10

Is anyone still experiencing this issue? I am getting 215 when updating status with and without image.


#11

Having the same issue when trying to upload video. Doing multipart/form-data request, generating Authentication header as described in documentation. When running test like showed in examples in docs - all generates correctly, but when changing to real values - getting this error. not sure what is wrong with authentication