Re: [twitter-dev] Re: Repeated connection request

2011-04-16 Thread Arnaud Meunier
Hey Konstantin,

OAuth is just an authorization/authentication mechanism. It's not handling
user sessions. You'll have to implement it on your side.

Now depending on what you want to do, you might be interested by web intents
as they'll handle sessions mechanism for you (automatically detecting if the
user is logged in to twitter.com and asking for login when necessary). Cf
http://dev.twitter.com/pages/intents

Arnaud / @rno



On Fri, Apr 15, 2011 at 6:54 PM, Konstantin rasf...@gmail.com wrote:

 I can save access_token, but how can I use it later?
 A user doesn't enter any information (login, email, etc), so I cannot
 get his access_token from the database.
 A user may login to Twitter under different accounts or may use
 another computer, so I cannot use cookies too.
 A user just clicks Sign in with Twitter button and I guess all
 further actions should be done by Twitter.

 On Apr 16, 12:13 am, m36tb6ll raeste...@gmail.com wrote:
  Did you save the access tokens of each user and use them whenever a
  user log-in to your site/app? If not, then they will be asked to allow
  the app everytime they login to your site.

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Repeated connection request

2011-04-15 Thread m36tb6ll

Did you save the access tokens of each user and use them whenever a
user log-in to your site/app? If not, then they will be asked to allow
the app everytime they login to your site.

Hope this helps...


On Apr 16, 3:07 am, Konstantin rasf...@gmail.com wrote:
 Hello!

 We are trying to implement the sign in with twitter button...we can
 successfully connect a twitter account and be redirected back to our
 site. But if a user comes back to our site who has already
 authorized our application and clicks the sign in with twitter button,
 they have to go through the allow our site access step again and
 reauthorize our application.

 Does anybody have any idea why this might be
 happening instead of what is described in step 3 
 onhttp://dev.twitter.com/pages/sign_in_with_twitter?

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Repeated connection request

2011-04-15 Thread Konstantin
I can save access_token, but how can I use it later?
A user doesn't enter any information (login, email, etc), so I cannot
get his access_token from the database.
A user may login to Twitter under different accounts or may use
another computer, so I cannot use cookies too.
A user just clicks Sign in with Twitter button and I guess all
further actions should be done by Twitter.

On Apr 16, 12:13 am, m36tb6ll raeste...@gmail.com wrote:
 Did you save the access tokens of each user and use them whenever a
 user log-in to your site/app? If not, then they will be asked to allow
 the app everytime they login to your site.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk