What is OpenID Connect?
See https://openid.net/connect/faq/ for a set of answers to Frequently Asked Questions about OpenID Connect.
How is OpenID Connect different than OpenID 2.0?
OpenID Connect performs many of the same tasks as OpenID 2.0, but does so in a way that is API-friendly. OpenID Connect can also be extended to include more robust mechanisms for signing and encryption. Integration of OAuth 1.0a and OpenID 2.0 required an extension (called the OpenID/OAuth hybrid); in OpenID Connect, OAuth 2.0 capability is built into the protocol itself.
List of Specifications
For the list of specifications and their status, please refer to the status page.
OpenID for Verifiable Credentials
One project of the OpenID Connect working group is the OpenID for Verifiable Credentials work. See the OpenID for Verifiable Credentials page for more information.
The easiest way to monitor progress on the OpenID Connect 1.0 Specification is to join the mailing list at https://lists.openid.net/mailman/listinfo/openid-specs-ab.
Please note that while anyone can join the mailing list as a read-only recipient, posting to the mailing list or actively contributing to the specification itself requires the submission of an IPR Agreement. More information is available athttps://openid.net/intellectual-property. Make sure to specify the working group as “OpenID AB/Connect”, because this group is a merged working group and both names must be specified.
- Monday Meetings
- When: Tuesday 8am Japan Time every other week: (See the google calendar below)
- Where: https://www3.gotomeeting.com/join/695548174
- Thursday meetings
- When: Thursday 7am PDT every other week: (See the google calendar below)
- Where: https://www3.gotomeeting.com/join/181372694
- GoToMeeting software is available on Mac, PC, iPhone, and Android Phone.
- Using VoIP option of GoToMeeting is preferred. If you have to absolutely use plain old telephone some reason, here is the US phone number: +1 (773) 897-3000.
- Please Note: Number of the participation to the call is limited to 15 most active members at the discretion of the chair due to the number of lines available.
To submit an issue to the specifications, use the following syntax in the issue title:
<SpecAbbrev> <Section.Number> - <Description>
For example, to submit a comment on section 4.3.2 of the Core spec, write the title as
Core 4.3.2 - This is the title for the issue
<Component> values in the issue tracker are currently:
Working with the Repository
The working repository uses Git for version control. The server is at bitbucket.org.
To work on the repository, you need to do the following:
As a preparation:
- Fill in the Contribution Agreement so that you join “OpenID AB/Connect Working Group”.
- (If you do not already have one, create a Bitbucket account).
Then start working with the repository as:
- Clone the repository. (The command to use is on https://bitbucket.org/openid/connect/src/master )
Make sure that:
- You only do one edit per commit.
- You include the <command> and <issue number> in the commit message (see below).
For more details, see: https://confluence.atlassian.com/display/BITBUCKET/Bitbucket+101
When making a commit, use the following syntax for the commit messages so that the issues are linked to the commit.
<command> <issue id>
Fix #45 - Typo fixed
<command> can be one of the following:
close/closed/closes/closing/fix/fixed/fixes # resolves the issue
reopen/reopens/reopening # reopens the issue
addresses/re/references/ref/refs/see # adds a link to the changeset as a comment for the issue
<issue id> SHOULD be specified as