Created
July 5, 2013 03:29
-
-
Save cnsoft/5931455 to your computer and use it in GitHub Desktop.
Twitter oauth flow
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| I'm not familiar with this library, can you explain a bit more about how it interacts with OAuth? You're using some words here that don't really jive with OAuth: a token or key should never be present in any kind of "div" or "box" -- what's the usual sequence of events here? Are you doing some kind of page scraping? | |
| If you're using callback-based OAuth, the sequence should be: | |
| a) You ask for a request token | |
| b) You send the user for authorization | |
| c) They get sent to the oauth_callback you specified in step a | |
| d) You exchange the request token for an access token using the oauth_verifier you got in step c | |
| If you're using out-of-band based OAuth, the sequence should be: | |
| a) You ask for a request token | |
| b) You send the user for authorization | |
| c) The user sees a PIN code | |
| d) You present a UI to the user to ask for that PIN code | |
| e) You exchange the request token for an access token using the PIN value from the user as your oauth_verifier |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment