log inhelp

  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • You already know Dokkio is an AI-powered assistant to organize & manage your digital files & messages. Very soon, Dokkio will support Outlook as well as One Drive. Check it out today!

View
 

OpenID and OAuth Hybrid Extension

Page history last edited by Brian Kissel 14 years, 4 months ago

 

Contents

 

Status

Active

Recommended by specifications council and approved by the general membership.

 

Latest spec:

 

 

Background Information

OpenID has always been focused on how to enable user-authentication within the browser.  Over the last year, OAuth has been developed to allow authorization either from within a browser, desktop software, or mobile devices. Obviously there has been interest in using OpenID and OAuth together allowing a user to share their identity as well as grant a Relying Party access to an OAuth protected resource in a single step. A small group of people have been working on developing an extension to OpenID which makes this possible in a collaborative fashion within http://code.google.com/p/step2/. This small project includes a draft spec and Open Source implementations which the proposers would like to finalize within the OpenID Foundation. 

Working Group Name

OpenID OAuth Hybrid Working Group 

Purpose

Produce a standard OpenID extension to the OpenID Authentication protocol that provides a mechanism to embed an OAuth approval request into an OpenID authentication request to permit combined user approval. The extension addresses the use case where the OpenID Provider and OAuth Service Provider are the same service. To provide good user experience, it is important to present a combined authentication and authorization screen for the two protocols. 

Scope

The proposed work is as follows: 

  • Extend the OpenID authentication request/response and the assertion verification mechanism, to embed an OAuth approval request into an OpenID authentication request. Assuming  the OpenID Provider and OAuth Service Provider are the same service.
  • Insulation of each protocol from the other, both for backwards compatibility as well as to enable OpenID and OAuth to evolve and incorporate additional features without requiring reviews of the combined usage. Especially, to allow future support for unregistered OAuth consumers.
  • Security analysis and best practices 

Out of scope

  • The OpenID extension does not define an unregistered OAuth consumers mode, but instead ensures that such support would be possible by protocol insulation. The unregistered consumers mode should be defined separately in the OAuth specifications. 

Anticipated Contributions

Finalize the OpenID OAuth Extension spec (http://step2.googlecode.com/svn/spec/openid_oauth_extension/latest/openid_oauth_extension.html) as an official OpenID Extension. 

Proposed List of Specifications

OpenID OAuth Extension 1.0. Specification completion by Q1 2009. 

Anticipated audience or users of the work

  • OpenID Providers and Relying Parties
  • OAuth Consumers and Service Providers
  • Implementers of OpenID Providers and Relying Parties 

Language in which the WG will conduct business

English. 

Method of work

E-mail discussions on the working group mailing list and working group conference calls. 

Basis for determining when the work of the WG is completed

The work will be completed once it is apparent that maximal consensus on the protocol proposal has been achieved within the working group, consistent with the purpose and scope. 

Proposers

 

 

Initial Editors

  • Dirk Balfanz, balfanz@google.com, Google
  • Breno de Medeiros, breno@google.com, Google
  • David Recordon, recordond@gmail.com
  • Joseph Smarr, joseph@plaxo.com, Plaxo
  • Allen Tom, atom@yahoo-inc.com, Yahoo!

 

Comments (0)

You don't have permission to comment on this page.

Printable version