Re: [OAUTH-WG] OAuth PoP Implementation

2016-02-07 Thread Adam Renberg
Thank you for these proof of concept implementations. They were very interesting to read. On Sun, Feb 7, 2016, 09:28 Roland Hedberg wrote: > So, I’ve done the ’client creates key pair’ version instead :-/ > > For those who can read and understand Python you can find me > implementation attempt o

Re: [OAUTH-WG] OAuth PoP Implementation

2016-02-07 Thread Roland Hedberg
So, I’ve done the ’client creates key pair’ version instead :-/ For those who can read and understand Python you can find me implementation attempt on github as an extension to my oauth2/oidc implementation (https://github.com/rohe/pyoidc). You can look at the necessary support methods in: http

Re: [OAUTH-WG] OAuth PoP Implementation

2016-02-04 Thread Justin Richer
Hi Erik, responses inline. On 2/4/2016 4:20 AM, Erik Wahlström wrote: Hi, Good work Justin. I’ve also implemented (parts) of PoP tokens for the ACE WG oauth2 draft and made a lot of the same assumptions. See below. On 03 Feb 2016, at 23:47, Justin Richer > wrote:

Re: [OAUTH-WG] OAuth PoP Implementation

2016-02-04 Thread Erik Wahlström
Hi, Good work Justin. I’ve also implemented (parts) of PoP tokens for the ACE WG oauth2 draft and made a lot of the same assumptions. See below. > On 03 Feb 2016, at 23:47, Justin Richer wrote: > > Hi Everyone, > > I recently decided to put together an end to end implementation of at leas

[OAUTH-WG] OAuth PoP Implementation

2016-02-03 Thread Justin Richer
Hi Everyone, I recently decided to put together an end to end implementation of at least part of the proposed OAuth specs. I haven’t seen any other implementations of the whole system, so I wanted to see how viable this whole idea really. It’s done in Node.js (using Express.js) and it’s on GitH