Re: [OAUTH-WG] Shepherd Writeup for draft-ietf-oauth-spop-06.txt

2015-03-09 Thread Nat Sakimura
Finally, we added PKCE S256 support on our implementation. Best, Nat 2015年2月20日(金)、7:28 Brian Campbell bcampb...@pingidentity.com: I can't comment with any authority on product road-map (that's above my pay-grade) but I can speculate that we probably would support S256 eventually. On Wed,

Re: [OAUTH-WG] Shepherd Writeup for draft-ietf-oauth-spop-06.txt

2015-02-19 Thread Brian Campbell
I can't comment with any authority on product road-map (that's above my pay-grade) but I can speculate that we probably would support S256 eventually. On Wed, Feb 18, 2015 at 10:33 AM, Hannes Tschofenig hannes.tschofe...@gmx.net wrote: Thanks Brian for pointing me to Section 4.4.1 and to the

Re: [OAUTH-WG] Shepherd Writeup for draft-ietf-oauth-spop-06.txt

2015-02-18 Thread John Bradley
It was Google that wanted S256 to be mandatory for the AS to support. That makes it easier for the client. S256 is relatively new so not being supported yet is not surprising. Sent from my iPhone On Feb 18, 2015, at 12:15 PM, Torsten Lodderstedt tors...@lodderstedt.net wrote: We don't

Re: [OAUTH-WG] Shepherd Writeup for draft-ietf-oauth-spop-06.txt

2015-02-18 Thread torsten
Hi Hannes, our implementation supports the plain mode only. We just verified compliance of our implementation with the current spec. As the only deviation, we do not enforce the minimum length of 43 characters of the code verifier. kind regards, Torsten. Am 17.02.2015 17:48, schrieb Hannes

Re: [OAUTH-WG] Shepherd Writeup for draft-ietf-oauth-spop-06.txt

2015-02-18 Thread Hannes Tschofenig
Thanks for the info, Torsten. Your feedback raises an interesting question, namely what functionality the parties have to implement to claim conformance to the specification. Quickly scanning through the specification didn't tell me whether it is OK to just implement the plain mode or whether

Re: [OAUTH-WG] Shepherd Writeup for draft-ietf-oauth-spop-06.txt

2015-02-17 Thread Hannes Tschofenig
Hi Torsten, does this mean that your implementation is not compliant with the current version anymore or that you haven't had time to verify whether there are differences to the earlier version? Ciao Hannes On 01/31/2015 05:34 PM, Torsten Lodderstedt wrote: Deutsche Telekom also implemented

Re: [OAUTH-WG] Shepherd Writeup for draft-ietf-oauth-spop-06.txt

2015-02-17 Thread Hannes Tschofenig
Hi Brian, what is different between the version you guys implemented and the version that is currently documented in the latest version of the draft? Ciao Hannes On 01/30/2015 06:50 PM, Brian Campbell wrote: On Tue, Jan 27, 2015 at 9:24 AM, Hannes Tschofenig hannes.tschofe...@gmx.net

Re: [OAUTH-WG] Shepherd Writeup for draft-ietf-oauth-spop-06.txt

2015-01-31 Thread Torsten Lodderstedt
Deutsche Telekom also implemented an early version of the draft last year. Am 30.01.2015 um 18:50 schrieb Brian Campbell bcampb...@pingidentity.com: On Tue, Jan 27, 2015 at 9:24 AM, Hannes Tschofenig hannes.tschofe...@gmx.net wrote: 1) What implementations of the spec are you aware