[Openid-specs-ab] Cookbooks project

[Dominick Baier]

Any progress on that?

From: Nat Sakimura <sakimura at gmail.com<mailto:sakimura at gmail.com>>
Date: Montag, 3. November 2014 17:48
To: Mike Jones <Michael.Jones at microsoft.com<mailto:Michael.Jones at microsoft.com>>, "openid-specs-ab at lists.openid.net<mailto:openid-specs-ab at lists.openid.net>" <openid-specs-ab at lists.openid.net<mailto:openid-specs-ab at lists.openid.net>>
Cc: Dominick Baier <dominick.baier at thinktecture.com<mailto:dominick.baier at thinktecture.com>>
Subject: Re: [Openid-specs-ab] Cookbooks project

Yes. There could be other ways as well, but  "developers" link is a good starting point.

On Mon Nov 03 2014 at 8:31:25 Mike Jones <Michael.Jones at microsoft.com<mailto:Michael.Jones at microsoft.com>> wrote:
Is the intent to host this content off of the Developers dropdown menu at openid.net<http://openid.net>?

From: Openid-specs-ab [mailto:openid-specs-ab-bounces at lists.openid.net<mailto:openid-specs-ab-bounces at lists.openid.net>] On Behalf Of Dominick Baier
Sent: Monday, November 03, 2014 5:48 AM
To: Nat Sakimura; openid-specs-ab at lists.openid.net<mailto:openid-specs-ab at lists.openid.net>
Subject: Re: [Openid-specs-ab] Cookbooks project

We could volunteer for C# - we already have an extensive set of samples for the various flows here:

https://github.com/thinktecture/Thinktecture.IdentityServer.v3.Samples/tree/master/source/Clients

So I could also write some of that up.

From: Nat Sakimura <sakimura at gmail.com<mailto:sakimura at gmail.com>>
Date: Sonntag, 2. November 2014 07:51
To: "openid-specs-ab at lists.openid.net<mailto:openid-specs-ab at lists.openid.net>" <openid-specs-ab at lists.openid.net<mailto:openid-specs-ab at lists.openid.net>>
Subject: [Openid-specs-ab] Cookbooks project

Hi Connectors,

Having seen 'OpenID Connect is not so hard' session by Justin and Amazon sessions at IIW XIX, I started to feel that perhaps having language specific cookbooks would help developers a lot.

For example, we could write a cookbook for JavaScript public client with proper handling of state parameters, generation of cryptographic random, etc. with sample codes that can be copied to their projects. I am pretty sure that if we do not provide these, people are prone to write a client with Math.random or even worse -- a fixed string-- as nonce and state.

What do you think?

The first batch of language that I have in mind are:

- JavaScript
- PHP
- Python
- Ruby
- Java

Any volunteers to lead each project?

Nat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20141123/da6499d3/attachment.html>