Skip to content
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

Yahoo Boss Signature #182

Open
macedd opened this issue Jul 5, 2015 · 4 comments
Open

Yahoo Boss Signature #182

macedd opened this issue Jul 5, 2015 · 4 comments

Comments

@macedd
Copy link

macedd commented Jul 5, 2015

Despite being configured properly, headers sent, signature generated, etc
Yahoo boss api keep throwing an error

u'Please provide valid credentials. OAuth oauth_problem="signature_invalid", realm="yahooapis.com"

Here is the code

from rauth import OAuth1Service

key = ''
secret = ''

yahoo = OAuth1Service(
    name='yahoo',
    consumer_key=key,
    consumer_secret=secret)

session = yahoo.get_session()
req = session.request('GET', 'https://yboss.yahooapis.com/ysearch/web?q=search&start=0&format=json', True, 'yahooapis.com')

print req.json()
print req.request.body
print req.request.url
print req.request.headers

Sounds like the signature is not generating properly for the consumer

https://developer.yahoo.com/boss/search/boss_api_guide/oauth.html

@josuebrunel
Copy link

Hello @ThiagoF , may be you should give a shot to yahoo-oauth which based on rauth. It supports OAuth1 and OAuth2

@jmgamboa
Copy link

jmgamboa commented Feb 8, 2016

@ThiagoF ever resolve this? I do not see you the part where you are signing the request in your code

@macedd
Copy link
Author

macedd commented Feb 8, 2016

Couldnt solve. Think I've done my own class using requests_oauthlib

@josuebrunel
Copy link

@jmgamboa @ThiagoF could you please make sure you have the right consumer key and secret. The default consumer key and consumer secret won't work for. As for yahoo gemini, yahoo boss requires special credentials ( You need to pay for them ). If it still doesn't work you can check the issue #183

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants