Approve OpenID Connect Implementer’s Drafts!
OpenID Conenct Implementer’s Draft voting has finally started. We had a technical problem that delayed the start of the voting almost 23 hours, but as promised, we have started it on the Feb. 7, PST! So here it goes!
Voting Page ===>
The specifications in questions are:
The specifications are posted at these locations:
A description of OpenID Connect can be found at http://openid.net/connect/. The working group page is http://openid.net/wg/connect/.
The vote closes on Feb. 15.
OIDF Members, please go to the
voting page and vote early!
 Thanks Darin Richardson of Refresh Media for sorting this out quickly.
When you read the OpenID Connect Specifications, you might feel a little bit intimidated. That’s because they are written in “spec language” and they deal with corner cases, etc. Yet when you translate them into normal English and just concentrate on a “simple case”, it …
So it seems there is a little bit of confusion around what needs to be returned from which endpoint among the readers of OpenID Connect specification. It actually is pretty clear if you understand what OAuth 2.0 response_type parameter is, …
An OpenID Connect server is just an OAuth 2.0 server on steroids. What it does it to return the ID Token, which contains information about the authentication event for the user at the door, in addition to the Access Token. …
In the previous post, I wrote about HAL enhanced OAuth. Similar thing can be achieved by using JSON Schema. Many people claim that OAuth 2.0 is JSON and REST. Well, yes, it is RESTish, but not quite REST. It notably …
First of all, let me state an important assumption. Whether you or me, or the PC that I am writing this blog post, let us assume that they exist and not get into a philosophical issue of existence. Let such …