OAuth 2.0 implementation

Alec Taylor alec.taylor6 at gmail.com
Fri Jul 6 20:58:35 CEST 2012


Yeah, seems Twitter is still stuck on 1.0a...

But LinkedIn seems to support 1.0a for REST and 2 for JS:
https://developer.linkedin.com/apis

So that could be a definite contender for Sanction support

On Sat, Jul 7, 2012 at 4:49 AM, Demian Brecht <demianbrecht at gmail.com> wrote:
> No worries, thanks for the request.
>
> Unfortunately AFAIK (according to the OAuth provider list on Wikipedia),
> both Twitter and LinkedIn still use OAuth 1.0a, so until they hop on the
> OAuth 2.0 bandwagon, they won't be added.
>
> -----Original Message-----
> From: Alec Taylor [mailto:alec.taylor6 at gmail.com]
> Sent: Friday, July 06, 2012 11:42 AM
> To: Demian Brecht
> Cc: comp.lang.python at googlegroups.com; python-list at python.org
> Subject: Re: OAuth 2.0 implementation
>
> On Sat, Jul 7, 2012 at 1:38 AM, Demian Brecht <demianbrecht at gmail.com>
> wrote:
>> Supported provider list (with example code) is now:
>> * Facebook
>> * Google
>> * Foursquare
>> * bitly
>> * GitHub
>> * StackExchange
>> * Instagram
>>
>> Other providers may also be supported out of the box, but have been
> untested thus far.
>
> Looking good. Keep adding more to the list!
>
> I'd especially be interesting in seeing the 3-phase Twitter and LinkedIn
> auths added to the list.
>
> Also I'll be extending it a little more at some point to make it
> "friendlier" :P
>
> Thanks for merging my last pull-request,
>
> Alec Taylor
>



More information about the Python-list mailing list