On Apr 26, 12:33 pm, Ian Bicking <i...@colorstudy.com> wrote:
> On Sun, Apr 26, 2009 at 11:25 AM, Mike Lewis <mikelikes...@gmail.com> wrote:
> > I wrote some OAuth repoze plugins and whatnot. There's a demo here.
>
> >http://github.com/mikelikespie/oauth-repoze
>
> > I probably should refactor the OAuth and repoze modules out
> > eventually.
>
> > The code isn't the cleanest, so if anybody feels like tidying it up a
> > bit, I'll merge it upstream.
>
> > I've only tested it with twitter.
>
> I'm confused on the scope.  This is an OAuth client?  But it uses
> repoze.what or repoze.who?  Aren't those for the server interface?  I'm
> having a hard time figuring out quite what this is trying to do...
>
> --
> Ian Bicking  |  http://blog.ianbicking.org

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.

Please see 
http://apiwiki.twitter.com/Sign-in-with-Twitter?SearchFor=log+in+with+twitter&sp=1
for what I mean

If you need an example of what I mean, look at http://tweeptracker.com
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to