[Openid-specs-ab] Versions published incorporating edits decided upon during 30-Jun-11 spec call

Mike Jones Michael.Jones at microsoft.com
Fri Jul 1 23:14:53 UTC 2011

Per the last call you were on, I do plan to take a crack at moving the basic binding into the Core and Framework specs.  That hasn't happened yet.

The parts of the binding that pertain to the core won't need JWT.  The parts that pertain to the Framework obviously will.

I'd also be interested in specifics of what things that got moved to the Framework that you believe should go back to the core, per your earlier note.

Thanks for the detailed reading you're doing!

				-- Mike

-----Original Message-----
From: Breno de Medeiros [mailto:breno at google.com] 
Sent: Friday, July 01, 2011 4:03 PM
To: Mike Jones
Cc: openid-specs-ab at lists.openid.net
Subject: Re: [Openid-specs-ab] Versions published incorporating edits decided upon during 30-Jun-11 spec call

I am confused about the "HTTP Redirect Binding"

- The Core now includes too little to be useful on its own without the reference to HTTP Binding
- The HTTP Binding includes references to JWT which we agreed should not be necessary for basic implementations

Am I missing something?

On Fri, Jul 1, 2011 at 10:43, Mike Jones <Michael.Jones at microsoft.com> wrote:
> OpenID Connect Framework:
> http://openid.net/specs/openid-connect-framework-1_0.html
> OpenID Connect HTTP Redirect Binding:
> http://openid.net/specs/openid-connect-http-redirect-1_0.html
> OpenID Connect UserInfo Endpoint:
> http://openid.net/specs/openid-connect-userinfo-1_0.html
> Sources:  http://svn.openid.net/repos/specifications/connect/1.0/
>                                                             -- Mike
> _______________________________________________
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-ab


More information about the Openid-specs-ab mailing list