OpenID Connect is a suite of lightweight specifications that provide a framework for identity interactions via RESTful APIs.  The simplest deployment of OpenID Connect allows for clients of all types including browser-based, mobile, and javascript clients, to request and receive information about identities and currently authenticated sessions.   The specification suite is extensible, allowing participants to optionally also support encryption of identity data, discovery of the OpenID Provider, and advanced session management, including logout.

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

Below is the link to the HTML version of the working copies of the specifications.

• Messages - Lists all the messages that are used in OpenID Connect. You can use this to create a new Bindings of the Connect, such as OpenID Connect for XMPP.
• Standard - Full version of a HTTP / OAuth 2.0 binding. If you are implementing the server or full client, this is the spec you want to read.  References Messages.
• Basic Client Profile - A profile of the full OpenID Connect 1.0 Specification that is designed to be easy to read and implement for simple Relying Parties.
• Discovery - defines how user and server endpoints are discovered.
• Registration - defines how clients register with OpenID Providers.
• Session Management - describes how to manage sessions for OpenID Connect.
• OAuth 2.0 Multiple Response Type Encoding Practices

Participation

The easiest way to monitor progress on the OpenID Connect 1.0 Specification is to join the mailing list at http://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 at http://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. 

The working group specification repository is kept at  http://svn.openid.net/repos/specifications/connect/1.0/ . In this repository, only approved sub-versions are committed. If you want to live on the edge, go to http://hg.openid.net/connect/ where we keep edit by edit commits.  These edits make it into the SVN once they are approved by the editors.

Meeting Schedule

• Every Monday / Thursday 3:00pm Pacific Time
• GoToMeeting Address:
• Monday: https://www3.gotomeeting.com/join/695548174
• Thursday: https://www3.gotomeeting.com/join/181372694
• (Mac, PC, iPhone, Android Phone versions are available.)
• Using VoIP option of GoToMeeting  is preferred. If you have to absolutely use plain old telephone some reason, here is the US long distance number:  +1 (773) 897-3000
• Please Note: Number of the participation to the call is limited to 10 most active members at the discretion of the chair due to the number of lines available. 

Issue Tracking

To submit an issue to each specifications, use the following syntax in the Title.

 <SpecAbbrev> - <Section.Number> <Descritpion>. 

For example, to submit a comment on section 4.3.2 of Message spec, write the title as

 Message - 4.3.2 This is the title for the issue 

The <SpecAbbrev> right now are:

• Messages
• Standard
• Basic
• Discovery
• Registration
• Session
• General

Link to the Issues

• General (All | Open ) – General issues not pertaining to a particular specification.
• Messages (All | Open)
• Standard (All | Open)
• Basic (All | Open)
• Discovery (All | Discovery)
• Registraion (All| Registration)
• Session Management (All | Open )

Working with the repository

The working repository of this WG uses Mercurial for the version control. The server uses bitbucket.

To work on the repository, you need to do the following:

As a preparation:

1. Fill in the Contribution Agreement so that you join ”OpenID AB/Connect Working Group.”
2. (If you have not already done so, install Mercurial.)
• CUI: http://mercurial.selenic.com/
• GUI: http://tortoisehg.org/
3. (If you do not already have, create Bitbucket userid).
4. Tell Nat/Mike/John the userid – they you will get a write previllege.

Then start working with the repository as:

1. Clone the repository. (Command to use is on http://hg.openid.net/connect/ )
2. hg pull
3. (edit a file)
4. hg commit -m ‘fix #45 – typo’
5. hg push

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: http://confluence.atlassian.com/display/BITBUCKET/Bitbucket+101

Commit Messages

When making a commit, use the following syntax for the commit messages so that the issues are linked to the commit.

<command> <issue id> 

For example,

 Fix #45 - Typo fixed. 

<command> can be one of the followings:

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 

The <issue id> SHOULD be specified as #45 etc.