Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Problems with Google's OAuth

I had a Lisp application that used the cl-oauth library to contact Google's Blogger API. This worked fine until about a week ago, when suddenly it stopped working, refusing me access to the protected resource, getting errors like this: 401: Must authenticate to use 'default&#39 when I try to access the protected resource.

The URL that gets this response (generated by cl-oauth) is:

http://www.blogger.com/feeds/default/blogs?oauth_signature=KEtBmxpM%252FfIgcCjMpiCM9DxNeBs%253D&oauth_consumer_key=wuwei.name&oauth_token=1%252FhXeaTHEe2eumbBCvrjvUvsQhetK3VZ0skk8qy-bpFcc&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1325121590&oauth_nonce=898902330744558861&oauth_version=1.0

In other words, I can go through the whole authentication process, get an access token, but then the token doesn't work to access the resource.

So, I guess the question is, did Google change anything in the last week or so? Are they phasing out OAuth 1.0 or something? Any clues appreciated.

like image 310
mtraven Avatar asked Mar 23 '26 02:03

mtraven


1 Answers

in fact the cl-oath was fixed. There was a change in drakma, which wasn't quite backwardly compatible. It did break cl-twitter as the poster Ramarran pointed out but things should be back to normal now

like image 159
fons haffmans Avatar answered Mar 24 '26 15:03

fons haffmans



Donate For Us

If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!