The OpenID membership has approved the following specifications as OpenID Implementer’s Drafts in the vote held from July 23 and July 30, 2013
- 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.
The voting results were:
- Approve (55 votes)
- Disapprove (0 votes)
- Abstain (2 votes)
Total Votes: 57 (out of 245 members = 23% > 20% quorum requirement)
An Implementer’s Draft is a stable version of a specification providing intellectual property protections to implementers of the specification. The working group intends for the final specifications to be compatible with these Implementer’s Drafts.
The approved Implementer’s Drafts are available at:
A description of OpenID Connect can be found at http://openid.net/connect/
. The working group page is http://openid.net/wg/connect/