Re-authorization on Twitter


Warning: count(): Parameter must be an array or an object that implements Countable in /home/styllloz/public_html/qa-theme/donut-theme/qa-donut-layer.php on line 274
0 like 0 dislike
2 views
How to organize re-authorize via Twitter? That is, the user already 1N time gave access for the application, did things and went out (logout). Now he comes again presses the button "login" and clearly does not want more time to get to the page with the confirmation of the legality of the actions of our apps, and want to enter the system. So how to organize it?

To store secret key in cookies and don't want to, because it somehow nebezpecna, are there any other ways? Twitpic, for example, loginit no questions asked of the user that is currently logged in to Twitter (if the course already has been confirmed for a twitpic account), there is a suspicion that he's looking cookies twitter.com.
by | 2 views

1 Answer

0 like 0 dislike
Well, in this case, from Twitter depends nothing. His job — to give you oauth_secret and oath_key, and then you can either keep or not keep. Accordingly, the request is sent encrypted using those keys — then logged in, the request is sent without keys — denay. So the question is, where to store your keys already, and encode them (ie logged in) or not to sign the request them (read — razaghian) have your task.
\r
First specify on what write and what threebets, and I did yuzhl conclusion on the word "cookies" about what you are confirming on their website. Yes?
by

Related questions

0 like 0 dislike
1 answer
0 like 0 dislike
1 answer
0 like 0 dislike
1 answer
0 like 0 dislike
1 answer
110,608 questions
257,186 answers
0 comments
27,859 users