OpenID Connect 1.0 Official Working Repository
Here are the specs that the AB/Connect Working Group is working on.List of Specifications
Below is the link to the HTML version of the working copies of the specifications.
- Basic Client Profile - A profile of the full OpenID Connect 1.0 Specification that is designed to be easy to read and implement for Relying Parties.
- Standard - Full version of a HTTP binding. References Messages.
- 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.
- 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
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
This working repository uses Mercurial for the version control. The server uses bitbucket.
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 have not already done so, install Mercurial.)
- (If you do not already have, create Bitbucket userid).
- Tell Nat/Mike/John the userid - they you will get a write previllege.
Then start working with the repository as:
- Clone the repository. (Command to use is on http://hg.openid.net/connect/ )
- hg pull
- (edit a file)
- hg commit -m 'fix #45 - typo'
- 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.