{"id":317,"date":"2011-07-23T20:09:24","date_gmt":"2011-07-23T20:09:24","guid":{"rendered":"http:\/\/www.sitekickr.com\/blog\/?p=317"},"modified":"2011-07-23T20:09:24","modified_gmt":"2011-07-23T20:09:24","slug":"oauth-1-0-troubleshooting","status":"publish","type":"post","link":"https:\/\/www.sitekickr.com\/blog\/oauth-1-0-troubleshooting\/","title":{"rendered":"OAuth 1.0 troubleshooting"},"content":{"rendered":"

It's my personal opinion that OAuth 2.0 came about primarily to address the mental anguish of developers who have struggled with OAuth 1.0.<\/p>\n

The majority of the issues are probably related to improperly creating the signature, but there are a few lesser known and lesser documented issues.<\/p>\n

If you're getting the overly vague "Could not authenticate with OAuth", these suggestions might help:<\/p>\n

    \n
  1. Make sure that you're using the correct method (GET \/ POST). That is, make sure the method you are using is appropriate for the request your making and that it matches the method in the signature.<\/li>\n
  2. Don't depend on a library for a given application to be 100% correct. It may be written for a specific use case, so you may need to do a little debugging.<\/li>\n
  3. Check if your parameters need to be URL encoded.<\/li>\n
  4. Verify that your parameters are in the correct order and have the correct case before being signed.
    \n\t\t <\/li>\n<\/ol>\n

    More specific troubleshooting can be found for the following services:<\/p>\n