{"id":976,"date":"2013-03-27T03:00:34","date_gmt":"2013-03-27T10:00:34","guid":{"rendered":"https:\/\/self-issued.info\/?p=976"},"modified":"2013-03-27T03:00:34","modified_gmt":"2013-03-27T10:00:34","slug":"third-release-candidates-for-openid-connect-implementers-drafts","status":"publish","type":"post","link":"https:\/\/self-issued.info\/?p=976","title":{"rendered":"Third Release Candidates for OpenID Connect Implementer’s Drafts"},"content":{"rendered":"

\"OpenID<\/span>A third set of Release Candidates for the pending OpenID Connect Implementer’s Drafts have been released. Like the first set, the second set of Release Candidates<\/a>, which were published earlier this month, also received thorough review, resulting in a smaller set of additional refinements. The changes primarily made some the claim definitions more precise and provided more guidance on support for multiple languages and scripts.<\/p>\n

Were it not for a set of pending changes about to be made to the JSON Object Signing and Encryption (JOSE) specifications<\/a>, this set of specifications would likely actually be the Implementer’s Drafts. However, the OpenID Connect working group made the decision to have those (non-breaking) JOSE changes be applied before we declare that the Implementer’s Drafts are done. Expect announcements about both the JOSE updates and the OpenID Connect Implementer’s Drafts soon.<\/p>\n

The new specifications are:<\/p>\n