Hey man, good morning.

If you are developing a web app, OAUTH is the way to go.

I am using Twitter4J but for sure oauth-python-twitter has methods to
do the same, this is what I do:

1) Generate the authorization url using the twitter account of the app

2) I redirect the user to that URL which is twitter login form

3) Twitter redirects the user to a callback url I set up in the app
account with the authentication tokens

4) I store those auth token in a DB where I also have the user profile

5) Whenever I want to communicate with Twitter I retrieve those tokens
from the storage and use them.

This is the app I am working on in case you wanna check the flow.


On Feb 4, 7:34 am, Jorge Vargas <jorge.var...@gmail.com> wrote:
> Hello,
> I'm a bit confused about how to go with this. Normally i'll expect a openID
> provider and then I'll code a consumer, 
> howeverhttp://apiwiki.twitter.com/Sign-in-with-Twitterpoints out I need to run
> oauth. Also several searches point out that twitter will not be an openID
> provider anytime soon.
> So my question is how will you handle twitter-only accounts, for this
> particular app you *must* have a twitter account and I want to store
> additional info regarding each user in my app. In order words all I need to
> know is that you are who you claim to be on twitter to attribute actions on
> you. Should I got with oauth even though that's overkill in this particular
> application?
> If that is the case any one has 
> usedhttp://code.google.com/p/oauth-python-twitteris it a good implementation?

Reply via email to