On Mon, Apr 27, 2009 at 6:52 PM, Mike Lewis <mikelikes...@gmail.com> wrote:
> Sorry for the confustion. It essentially contains 3 things. > - An oauth client (uses SA as a store) which could be used outside of > pylons, repoze, or even wsgi > - A repoze.who plugin that uses the OAuth client. I used the OpenID > repoze.who plugin as a starting point since i never wrote one before. > It's a similar idea. The "user id" ends up being the token they get > back from twitter > - repoze.what auth that uses the the repoze.who plugin and an example > of it protecting a class. > > I created it to use for a website that uses OAuth for authentication > from twitter. Even though OAuth is meant for authentication I believe, > twitter intends it to be used as authentication for other sites as > well. > Ah, that explains why it seemed confusing to me ;) I always thought of persistently associating the authorized request token with the user account, but I suppose you could just get a new request token each time to do both kinds of auth at the same time. Huh, interesting. -- Ian Bicking | http://blog.ianbicking.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en -~----------~----~----~----~------~----~------~--~---
