Skip navigation

we only expect the
oauth_verifier to be present on the access_token step for applications
that have indicated the desktop “PIN code” flow

In this respect Twitter is not compliant with the oauth specification. When your callback is called from Twitter via the oauth authentication flow for application type “Browser” (what you selected in your settings for your application in twitter.com/oauth) you only get the oauth_token, and that’s all you need to pass when you attempt to get the access token.

Posted via web from Apphacker’s learning curve

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: