Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #22222 > unrolled thread

OAuth 2.0 implementation

Back to article view | Back to comp.lang.python

Contents

  OAuth 2.0 implementation Demian Brecht <demianbrecht@gmail.com> - 2012-03-26 19:42 -0700
    Re: OAuth 2.0 implementation Ben Finney <ben+python@benfinney.id.au> - 2012-03-27 14:11 +1100
      Re: OAuth 2.0 implementation Roy Smith <roy@panix.com> - 2012-03-26 23:30 -0400
        Re: OAuth 2.0 implementation Ben Finney <ben+python@benfinney.id.au> - 2012-03-27 14:49 +1100
          Re: OAuth 2.0 implementation Roy Smith <roy@panix.com> - 2012-03-26 23:57 -0400
            Re: OAuth 2.0 implementation Ben Finney <ben+python@benfinney.id.au> - 2012-03-27 15:24 +1100
              Re: OAuth 2.0 implementation Jack Diederich <jackdied@gmail.com> - 2012-03-27 01:24 -0400
              Re: OAuth 2.0 implementation Demian Brecht <demianbrecht@gmail.com> - 2012-03-26 22:30 -0700
                Re: OAuth 2.0 implementation Roy Smith <roy@panix.com> - 2012-03-27 10:18 -0400
                  Re: OAuth 2.0 implementation Demian Brecht <demianbrecht@gmail.com> - 2012-03-27 10:54 -0700
                  Re: OAuth 2.0 implementation Mark Hammond <skippy.hammond@gmail.com> - 2012-03-28 14:42 +1100
      Re: OAuth 2.0 implementation Stuart Bishop <stuart@stuartbishop.net> - 2012-03-27 16:59 +0700
      Socket Error : Address still in use  (Conveting from python 1.5.2 to 2.7.1) Wong Wah Meng-R32813 <r32813@freescale.com> - 2012-03-27 09:41 +0000
      Re: OAuth 2.0 implementation Roland Hedberg <roland@catalogix.se> - 2012-03-27 15:36 +0200
    Re: OAuth 2.0 implementation Demian Brecht <demianbrecht@gmail.com> - 2012-07-05 07:06 -0700
      Re: OAuth 2.0 implementation Alec Taylor <alec.taylor6@gmail.com> - 2012-07-06 01:19 +1000
        Re: OAuth 2.0 implementation Demian Brecht <demianbrecht@gmail.com> - 2012-07-05 10:48 -0700
        Re: OAuth 2.0 implementation Demian Brecht <demianbrecht@gmail.com> - 2012-07-05 10:48 -0700
          Re: OAuth 2.0 implementation Demian Brecht <demianbrecht@gmail.com> - 2012-07-06 08:38 -0700
          Re: OAuth 2.0 implementation Demian Brecht <demianbrecht@gmail.com> - 2012-07-06 08:38 -0700
            Re: OAuth 2.0 implementation Alec Taylor <alec.taylor6@gmail.com> - 2012-07-07 04:41 +1000
            RE: OAuth 2.0 implementation "Demian Brecht" <demianbrecht@gmail.com> - 2012-07-06 11:49 -0700
            Re: OAuth 2.0 implementation Alec Taylor <alec.taylor6@gmail.com> - 2012-07-07 04:58 +1000

Page 2 of 2 — ← Prev page 1 [2]

#24984

On Sat, Jul 7, 2012 at 1:38 AM, Demian Brecht <demianbrecht@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

[toc] | [prev] | [next] | [standalone]

#24985

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@gmail.com] 
Sent: Friday, July 06, 2012 11:42 AM
To: Demian Brecht
Cc: comp.lang.python@googlegroups.com; python-list@python.org
Subject: Re: OAuth 2.0 implementation

On Sat, Jul 7, 2012 at 1:38 AM, Demian Brecht <demianbrecht@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

[toc] | [prev] | [next] | [standalone]

#24986

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@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@gmail.com]
> Sent: Friday, July 06, 2012 11:42 AM
> To: Demian Brecht
> Cc: comp.lang.python@googlegroups.com; python-list@python.org
> Subject: Re: OAuth 2.0 implementation
>
> On Sat, Jul 7, 2012 at 1:38 AM, Demian Brecht <demianbrecht@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
>

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | comp.lang.python

csiph-web