-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OAuth 2-legged request gets "signature_invalid" #16
Comments
It looks like the oauth gem does not properly handle url query parameters. I was able to generate the request by hand like this:
Which is quite a bit of work to do for something so simple. |
This bug disappeared in 0.4.1 |
I still see this bug. |
U used oauth 0.4.1 and this: and it worked. |
Can you provide an example of submitting the above YQL query, as I did in the initial bug report? |
check out his git repo. Looks like he is not using half of the shit you put in your initial request. But there is some extra verify shit which is not part of standard oauth. All this stuff is beyond me for a moment, I just need to upload my bookmarks to delicious. |
Looking at his implementation of access_token.get : http://github.com/floehopper/delicious-api-via-oauth/blob/master/oauth-extensions/delicious/access_token.rb#L17 it looks like he just creates a URL, forming the exact style of request I made in my initial post. So, it must be that the https://api.login.yahoo.com/oauth/v2 interface is not the same as the http://query.yahooapis.com/v1/yql interface. Not surprising. So, bug still exists. |
I stumbled upon this problem too. I'm trying to implement 2-legged authentication Gmail IMAP. The API requires a query parameter to be included in the url for signing: |
Based on this working example: http://paul.donnelly.org/demos/oauth.htm
I tried to do the same thing from Ruby with the oauth gem, but I get "signature_invalid":
produces:
oauth-0.3.6/lib/oauth/consumer.rb:167:in
request': signature_invalid (OAuth::Problem)Perhaps I'm just forming the request improperly. Any ideas?
The text was updated successfully, but these errors were encountered: