For the record... A few months ago I've developed an Oauth2 provider based in Pyramid too. It works with the resource owner password credentials flow. This flow is not the most popular oAuth flow, but it's useful in case that we want to oAuth enable an app or a set of apps in an scenario with an already existing user backend. Using this flow you can use Osiris as a gateway between your existing user store and oAuth enable it. Osiris will authenticate the user credentials against your user store and if suceeds it will issue a oAuth token. Then, an app can use it to impersonate the user's token to access an oAuth enabled REST API, for example.
You can find more information here: https://github.com/sneridagh/osiris I haven't give it any love in the last months, but it works. Hey Yaco guys! Great job! It's possible to make the oauth2 provider work standalone? Which flows implement? Cheers, -- Víctor Fernández de Alba http://about.me/victorfernandezdealba Twitter/IRC: sneridagh g+/Facebook: victorfda On Wed, Sep 12, 2012 at 8:15 PM, Lorenzo Gil Sanchez < lorenzo.gil.sanc...@gmail.com> wrote: > > We have developed a simple oauth2 backend at: > > https://github.com/Yaco-Sistemas/yith-library-server/tree/master/yithlibraryserver/oauth2 > > It's still work in progress but we are using it in our beta instance at: > > https://yithlibrary-webclient.herokuapp.com/ > > so you can play with it and see how it works > > 2012/9/12 Andrija Frinčić <bob.rock...@gmail.com>: > > Hi Kevin > > > > Is there any sample available or at least basic documentation? We would like > > to include oauth2 provider to a pyramid based backend application we are > > developing. > > > > Best regards > > > > > > On Tuesday, August 9, 2011 8:29:00 AM UTC+2, Kevin Van Wilder wrote: > >> > >> Hi there, > >> > >> We are currently developing an open source OAuth 2.0 provider extension > >> for pyramid and are aiming for full integration of draft 18 down the line. > >> > >> Currently we are focusing on the "client_credentials" grant type, the most > >> simple type of communication between a consumer and its provider, requiring > >> no intervention of the resource owner, i.e. the user. After this, we will > >> fine-tune all the aspects before moving on to implement the other grant > >> types. > >> > >> The docs and tests are currently lacking, but they will soon find its way > >> on the repository. > >> > >> If you are interested in helping us, don't hesitate to contact me! As > >> always, feedback is much appreciated. > >> > >> Kind regards, > >> > >> Kevin Van Wilder > >> http://www.tick.ee > >> > > -- > > You received this message because you are subscribed to the Google Groups > > "pylons-devel" group. > > To view this discussion on the web visit > > https://groups.google.com/d/msg/pylons-devel/-/GqQyIem_eTwJ. > > > > 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. > > -- > 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. > -- 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.
