Loading Profile...
Does the reference oauth python module and example code need to be updated with respect to 1.0a spec?
Does the reference oauth python module and example code need to be updated with respect to 1.0a spec? I'm referring to the one that's used by http://oauth.googlecode.com/svn/code/... I've been attempting to create a twitter-oauth library and failing miserably because I know not where to plug in the number the provider gives after authentication.
I’m frustrated
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?The example should work okay with 1.0a. What number are you referring to?1 Comment
Add a comment
This answers the question
-
As i understand it, the new servers need to give a challenge number to the user to input into the client, which would then do something with the server with this number. There'd also be a timeout or something on this number. -
Inappropriate?The Pin number you get is the verifier code - you need to make a new request and send it back to get the access token - here is some interactive code if it makes it any more transparent:
>>> verifier= 8650863
>>> ACCESS_URL='http://twitter.com/oauth/access_token'
>>> oauth_request = oauth.OAuthRequest.from_consumer_and_token(consumer,token=token,verifier=verifier,http_url=ACCESS_URL)
>>> oauth_request.sign_request(signature_method, consumer,token)
>>> connect=httplib.HTTPConnection('twitter.com')
>>> connect.request(oauth_request.http_method, ACCESS_URL,headers=oauth_request.to_header())
that should return the new token
