AB/Connect Working Group

What is OpenID Connect?

OpenID Connect is a suite of lightweight specifications that provide a framework for identity interactions via REST like 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.

See http://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.

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 SVN once they are approved by the editors.

Meeting Venue and Schedule

iCal Link:

  • Monday Meetings
  • Thursday meetings
  • 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.

Issue Tracking

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

 <SpecAbbrev> <Section.Number> - <Description>

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> values at present are:

  • Core
  • Discovery
  • Registration
  • Session
  • Basic
  • Implicit
  • All

Working with the bitbucket 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.)
  3. (If you do not already have one, create a Bitbucket userid).
  4. Tell Nat/Mike/John the userid – they will get you write privileges.

Then start working with the repository as:

  1. Clone the repository. (The 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 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

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