The 60-day public review of the final OpenID Connect Core specifications has begun.
The drafts under public review are as follows.
- OpenID Connect Core – Defines a secure and privacy-conscious way to convey authentication information and end-user attributes based on OAuth 2.0, the core functionality of OpenID Connect.
- OpenID Connect Discovery – Defines the procedures by which an RP dynamically discovers an OpenID Provider.
- OpenID Connect Dynamic Registration – Defines the procedures by which an RP dynamically registers itself with an OpenID Provider.
- OAuth 2.0 Multiple Response Types – Defines several new OAuth 2.0 response types specific to OpenID Connect.
This 60-day public review is the period defined in the OpenID Foundation’s OpenID Process. It also accommodates the comment period required by Article L of Annex Three to the Agreement on Technical Barriers to Trade (WTO TBT Agreement)[1], which lasts 60 days.
This comment period is scheduled to end on February 18, 2014. Unless technical issues are discovered during the comment period and the WG determines that the drafts must be revised to resolve them, a 7-day voting period will follow. OpenID Foundation members will vote on whether to make these drafts Final Specifications. Notice of the vote will be given by 2/18 (Tue), no later than 2 weeks in advance, and voting will close on February 25, 2014 (Tue).
Information about OpenID Connect is available at http://openid.net/connect/. The WG page is athttp://openid.net/wg/connect/. For information on joining the OpenID Foundation, please seehttps://openid.net/foundation/members/registration. If you are not yet a member, please consider joining and participating in the approval vote.
Please submit feedback on the specifications as follows.
- http://openid.net/intellectual-property/ Sign the contribution agreement at (please specify in the contribution agreement that you are joining the “AB+Connect” WG).
- Join the WG mailing list at http://lists.openid.net/mailman/listinfo/openid-specs-ab.
- Post your feedback to the mailing list.
Although this process is somewhat cumbersome, it is a necessary safeguard to ensure that all commenters waive enforcement of intellectual property rights against implementations of these specifications, allowing implementers to use them freely without being charged patent royalties or similar fees. Thank you for your understanding.
See you again!
[1] The original is URUGUAY ROUND AGREEMENT Agreement on Technical Barriers to Trade.
Related posts
Financial-grade API (FAPI) Security Profile Parts 1 and 2, and JWT Secured Authorization Response Mode (JARM), Have Entered Public Review Prior to the Implementer’s Draft Vote.
The OpenID Financial-grade API Working Group has recommended that the following draft specifications be approved as OpenID Implementer's Drafts. Financial-grade API - Part 1: Read-Only API…
Public Review of “Financial API – Part 1: Read Only API Security Profile” Has Begun
The OpenID Foundation’s Financial API (FAPI) Working Group has recommended commencing a public review prior to the vote to approve Financial API – Part 1: Read Only API…
? It’s finally here! The final specification review for FAPI 2.0 Message Signing has begun!
Announced May 29, 2025 - A new member of the OpenID family is ready to join us! ? What's happening? We have exciting news from the…