Specifications

OpenID specifications are developed by OpenID working groups and go through three phases: Drafts, Implementer’s Drafts, and Final Specifications. Implementer’s Drafts and Final Specifications provide intellectual property protections to implementers. Final Specifications are OpenID Foundation standards.

Final Specifications

OpenID Connect specifications:

• OpenID Connect Core – Defines the core OpenID Connect functionality: authentication built on top of OAuth 2.0 and the use of claims to communicate information about the End-User
• OpenID Connect Discovery – (Optional) Defines how clients dynamically discover information about OpenID Providers
• OpenID Connect Dynamic Registration – (Optional) Defines how clients dynamically register with OpenID Providers
• OAuth 2.0 Multiple Response Types – Defines several specific new OAuth 2.0 response types
• OAuth 2.0 Form Post Response Mode – (Optional) Defines how to return OAuth 2.0 Authorization Response parameters (including OpenID Connect Authentication Response parameters) using HTML form values that are auto-submitted by the User Agent using HTTP POST
• OpenID 2.0 to OpenID Connect Migration 1.0 – (Optional) Defines how to migrate from OpenID 2.0 to OpenID Connect

Implementer’s Drafts

OpenID Connect and OpenID Connect-related specifications:

• Session Management – (Optional) Defines how to manage OpenID Connect sessions, including postMessage-based logout functionality
• Health Relationship Trust Profile for OAuth 2.0HEART OAuth 2.0 Profile
• Health Relationship Trust Profile for OpenID Connect 1.0HEART OpenID Connect Profile
• Health Relationship Trust Profile for User Managed Access 1.0HEART UMA Profile

Drafts

• Front-Channel Logout – (Optional) Defines a front-channel logout mechanism that does not use an OP iframe on RP pages
• Back-Channel Logout – (Optional) Defines a logout mechanism that uses back-channel communication between the OP and RPs being logged out
• Account Chooser 1.0
• Native Applications Agent Core 1.0
• Native Applications Agent API Bindings 1.0
• OpenID Connect Profile for SCIM Services – (Optional) Defines how to use SCIM with OpenID Connect
• OpenID Connect Federation – (Optional) Defines how sets of OPs and RPs can establish trust by utilizing a Federation Operator
• MODRNA Discovery
• MODRNA Registration
• MODRNA Authentication Profile
• OpenID Connect Account Migration – (Optional) Specifies a protocol for migrating user accounts among OpenID Connect OPs
• Token Bound Authentication – (Optional) Defines how to apply Token Binding to OpenID Connect ID Tokens
• EAP ACR Values – (Optional) Enables OpenID Connect RPs to request that specific authentication context classes be applied to authentications performed and for OPs to inform RPs whether these requests were satisfied

Obsolete Specifications

Final OpenID 2.0 specifications:

• OpenID Authentication 2.0 (txt)
• OpenID Attribute Exchange 1.0 (txt)
• OpenID Provider Authentication Policy Extension 1.0 (txt)
• OpenID Simple Registration Extension 1.0 (txt)
• Yadis Discovery Protocol (Developed separately from OpenID, though used in 2.0)

OpenID 2.0 Drafts:

• OpenID Simple Registration Extension 1.1 – Draft 1 (txt)
• Contract Exchange 1.0

Early OpenID specifications:

• OpenID Authentication 1.1 (txt)
• OpenID Authentication 1.1 (original format)
• OpenID Authentication 1.0 (original format)

Libraries

The Libraries page lists libraries that implement OpenID Connect and related specifications.

See the OpenID Connect page for more information about OpenID Connect.