Review of Proposed Second OpenID Connect Implementer’s Drafts

Published June 7, 2013
The OpenID Connect Working Group recommends approval of the following specifications as OpenID Implementer’s Drafts:
  • Basic Client Profile – Simple, self-contained profile for a Web-based Relying Parties using the OAuth code flow.
  • Implicit Client Profile – Simple, self-contained profile for a Web-based Relying Parties using the OAuth implicit flow.
  • Messages – Defines the messages that are used by OpenID Connect.
  • Standard – Defines an HTTP binding for the Messages, for both Relying Parties and OpenID Providers.
  • Discovery – Defines how Relying Parties dynamically discover information about OpenID Providers.
  • Dynamic Registration – Defines how Relying Parties dynamically register with OpenID Providers.
  • Session Management – Defines how to manage OpenID Connect sessions, including logout functionality.
  • Multiple Response Type Encoding – Registers OAuth 2.0 “response_type” values used by OpenID Connect.
An Implementer’s Draft is a stable version of a specification providing intellectual property protections to implementers of the specification. This note starts the 45 day public review period for the specification drafts in accordance with the OpenID Foundation IPR policies and procedures. This review period will end on Monday, July 22, 2013. Unless issues are identified during the review that the working group believes must be addressed by revising the drafts, this review period will be followed by a seven day voting period during which OpenID Foundation members will vote on whether to approve these drafts as OpenID Implementer’s Drafts. These specifications are available at: A description of OpenID Connect can be found at The working group page is Information on joining the OpenID Foundation can be found at If you’re not already a member, please consider joining to participate in the approval vote. You can send feedback on the specifications in a way that enables the working group to act upon your feedback by (1) signing the contribution agreement at to join the working group (please specify that you are joining the “AB+Connect” working group on your contribution agreement), (2) joining the working group mailing list at, and (3) sending your feedback to the list. UPDATE: The working group has updated some of the specifications to apply errata identified during the review period. The working group recommends that these versions be used for the Implementer’s Drafts. Any contributor may request that the 45 day review period be restarted based upon these updates, however the working group does not believe that this is necessary due to the minimal size and nature of the changes. The original versions of the proposed Implementer’s Drafts are posted at the locations below to facilitate comparison between the original versions and those with the errata applied: