Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #76320 > unrolled thread
| Started by | Richard Prosser <ebizbytes@gmail.com> |
|---|---|
| First post | 2014-08-14 09:49 -0700 |
| Last post | 2014-09-02 12:15 +0200 |
| Articles | 3 — 3 participants |
Back to article view | Back to comp.lang.python
Which OAuth library? Richard Prosser <ebizbytes@gmail.com> - 2014-08-14 09:49 -0700
Re: Which OAuth library? Chris “Kwpolska” Warrick <kwpolska@gmail.com> - 2014-08-14 19:54 +0200
Re: Which OAuth library? Roland Hedberg <roland.hedberg@adm.umu.se> - 2014-09-02 12:15 +0200
| From | Richard Prosser <ebizbytes@gmail.com> |
|---|---|
| Date | 2014-08-14 09:49 -0700 |
| Subject | Which OAuth library? |
| Message-ID | <1a2f3320-79eb-4055-a933-ea474595976e@googlegroups.com> |
I "need" one for use with Flask, as I don't really have time to implement my own. Initially this will be for the "Two-Legged" case but I may well have to support the "Three-Legged" version later on. "Open ID Connect" may also be an option eventually. The basic idea is to provide an authorization/authentication service in a fairly conventional manner. My boss has told me to use OAuth, probably because he has experience with it and also to allow for third-party transactions. However it is not clear to me how I should decide between the various packages on offer. Any advice from experienced/informed users would be very welcome. Thanks ... Richard
[toc] | [next] | [standalone]
| From | Chris “Kwpolska” Warrick <kwpolska@gmail.com> |
|---|---|
| Date | 2014-08-14 19:54 +0200 |
| Message-ID | <mailman.13007.1408038866.18130.python-list@python.org> |
| In reply to | #76320 |
[Multipart message — attachments visible in raw view] — view raw
On 14 August 2014 18:51 "Richard Prosser" <ebizbytes@gmail.com> wrote: > > I "need" one for use with Flask, as I don't really have time to implement my own. You should not implement things on your own if there are existing and same implementations. > Initially this will be for the "Two-Legged" case but I may well have to support the "Three-Legged" version later on. "Open ID Connect" may also be an option eventually. > > The basic idea is to provide an authorization/authentication service in a fairly conventional manner. My boss has told me to use OAuth, probably because he has experience with it and also to allow for third-party transactions. > > However it is not clear to me how I should decide between the various packages on offer. Any advice from experienced/informed users would be very welcome. > > > Thanks ... > > Richard > -- > https://mail.python.org/mailman/listinfo/python-list Google hints at https://flask-oauthlib.readthedocs.org/en/latest/ and it's looking pretty good. There is also flask-oauth, but it seems quite outdated. -- Chris “Kwpolska” Warrick <http://chriswarrick.com/> Sent from my SGS3.
[toc] | [prev] | [next] | [standalone]
| From | Roland Hedberg <roland.hedberg@adm.umu.se> |
|---|---|
| Date | 2014-09-02 12:15 +0200 |
| Message-ID | <mailman.13711.1409653020.18130.python-list@python.org> |
| In reply to | #76320 |
14 aug 2014 kl. 19:54 skrev Chris “Kwpolska” Warrick <kwpolska@gmail.com>: > On 14 August 2014 18:51 "Richard Prosser" <ebizbytes@gmail.com> wrote: > > > > I "need" one for use with Flask, as I don't really have time to implement my own. > > You should not implement things on your own if there are existing and same implementations. > > > Initially this will be for the "Two-Legged" case but I may well have to support the "Three-Legged" version later on. "Open ID Connect" may also be an option eventually. > > > > The basic idea is to provide an authorization/authentication service in a fairly conventional manner. My boss has told me to use OAuth, probably because he has experience with it and also to allow for third-party transactions. > > > > However it is not clear to me how I should decide between the various packages on offer. Any advice from experienced/informed users would be very welcome. I’m responsible for one implementation (pyoidc) that is primary a OpenID connect implementation. But since OpenID Connect is a profile of OAuth2 it will work in an OAuth2 context too. This implementation is special in that it’s the de facto reference implementation for OpenID Connect. It’s that, due to the fact that I’ve built the OpenID Connect test suit which most today available OpenID Provider implementations have verified themselves against. — Roland ”Being able to think like a child is an important attribute of being an adult” - Eddie Izzard
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.python
csiph-web