We do the same thing.
A few notes:
* I run the authorization API as a standalone app/service, and also run the
read/write APIs as a third service. Our services have hit the api with
their endpoint in their path (ie /api/v1/app1 /api/v1/app2) so they can be
partitioned out later if needed and
I started an oauthlib integration a while back. It's not feature complete
and it's light on documentation, but if there's interest I would love to
see it grow. It is meant to make it easy to create an oauth provider.
https://github.com/tilgovi/pyramid-oauthlib
On Tue, Mar 14, 2017, 18:01 Jonathan
thanks for sharing those points.
I'm not sure how to transform the existing app. I'll have to clean the
base code a bit before passing to implementing this part.
I'll surely have more questions later on.
Le 15/03/2017 à 02:01, Jonathan Vanasco a écrit :
> We do the same thing.
>
> A few notes:
>
Have you tried https://github.com/elliotpeele/pyramid_oauth2_provider ?
It seems to miss some use cases but it covers quite well the oauth2 workflow
Le 15/03/2017 à 02:01, Jonathan Vanasco a écrit :
> We do the same thing.
>
> A few notes:
>
> * I run the authorization API as a standalone app/ser
On Friday, March 17, 2017 at 1:49:19 PM UTC-4, tonthon wrote:
>
> Have you tried https://github.com/elliotpeele/pyramid_oauth2_provider ?
> It seems to miss some use cases but it covers quite well the oauth2
> workflow
>
This looks a lot like my oauth1 solution.
--
You received this messag
