Geek Answers Handbook

Why do users need to enter a 7-digit Twitter PIN to provide access to my application?

I am introducing some rubies for rails cheat code for my users. I am creating the proper oauth link ... something like

http://twitter.com/oauth/authorize?oauth_token=y2RkuftYAEkbEuIF7zKMuzWN30O2XxM8U9j0egtzKv

But after my test account grants access to twitter, it will pull out a page with the message "You have successfully granted access." Just go back and enter the following PIN to complete the process. 1234567 "

I have no idea where the user should enter this PIN and why he should do it. I do not think that this should be a necessary step. Twitter should redirect the user to the callback URL that I specified in the application settings. Does anyone know why this is happening?

UPDATE I found in this article that says I need to send my users to this URL (check "authenticate" instead of "authorize"):

http://twitter.com/oauth/authenticate?oauth_token=y2RkuftYAEkbEuIF7zKMuzWN30O2XxM8U9j0egtzKv

I made changes, but Twitter redirects the user to the authorization path after he clicks “Allow”, which then gives him a 7-digit PIN code again!

+5
source share
4 answers

OAuth 1.0a OAuth 1.0 . PIN- , /iphone-. -, PIN- , .

, -, OAuth . , "", .

+6

oauth_callback URL-, , , . oauth_callback=oob .

+5

twitter . , .

+1

,

config.gem "twitter", :version => "0.6.12"

twitter

gem

config.gem "twitter", :version => "0.9.2"

.

GEM.

0
source

More articles:


All Articles