There is no need for second authorization. You need to save oauth token and
secret
in your db and use it next time he tries to login. These will be valid
unless he cancels
the connection with your application. Read more documentation at
https://docs.google.com/View?docID=dcf2dzzs_2339fzbfsf4 for
However, if you *want* to force the user to authorize each time,
there's an easy way to do that. Just don't save the tokens when you
get them from Twitter!
On Tue, Feb 2, 2010 at 7:37 AM, lalit goklani lgokl...@gmail.com wrote:
There is no need for second authorization. You need to save oauth
The Allow/Deny prompt should be displayed every time if you are using
https://twitter.com/oauth/authorize?oauth_token=xyz. The prompt should only
be skipped on subsequent authentications if you send users to
https://twitter.com/oauth/authenticate?oauth_token=xyz. Verify which one you
are using and
You can also use 'force_login=true' parameter passed along with token while
you are getting the authorization url for the link. That will
always make user to login to twitter irrespective of they are logged in.
--
Thanks.
Lalit
Twitter Facebook Application - http://www.twitsfb.com
Article
