Web Authorization Protocol
charter-ietf-oauth-05

WG review announcement

From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: oauth@ietf.org 
Subject: WG Review: Web Authorization Protocol (oauth)

The Web Authorization Protocol (oauth) WG in the Security Area of the
IETF is undergoing rechartering. The IESG has not made any determination
yet. The following draft charter was submitted, and is provided for
informational purposes only. Please send your comments to the IESG
mailing list (iesg@ietf.org by 2016-01-22.

Web Authorization Protocol (oauth)
-----------------------------------------------------------------------
Current status: Active WG

Chairs:
  Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
  Derek Atkins <derek@ihtfp.com>

Area Directors:
  TBD

Assigned Area Director:
  Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>

Mailing list:
  Address: oauth@ietf.org
  To subscribe: https://www.ietf.org/mailman/listinfo/oauth
  Archive: https://mailarchive.ietf.org/arch/browse/oauth/

Charter: https://datatracker.ietf.org/doc/charter-ietf-oauth/

The Web Authorization (OAuth) protocol allows a user to grant a
third-party web site or application access to the user's protected
resources, without necessarily revealing their long-term credentials,
or even their identity. For example, a photo-sharing site that
supports OAuth could allow its users to use a third-party printing web
site to print their private pictures, without allowing the printing
site to gain full control of the user's account and without having the
user share his or her photo-sharing sites' long-term credential with
the printing site.

The OAuth 2.0 protocol suite already includes

* a procedure for enabling a client to register with an authorization
  server,
* a protocol for obtaining authorization tokens from an authorization
  server with the resource owner's consent, and
* protocols for presenting these authorization tokens to protected
  resources for access to a resource.

This protocol suite has been enhanced with functionality for
interworking with legacy identity infrastructure (such as SAML), token
revocation, token exchange, dynamic client registration, token
introspection, a standardized token format with the JSON Web Token, and
specifications that mitigate security attacks, such as Proof Key for
Code Exchange.

The ongoing standardization efforts within the OAuth working group
focus on increasing interoperability of OAuth deployments and to
improve security. More specifically, the working group is defining proof
of possession tokens, developing a discovery mechanism, providing
guidance for the use of OAuth with native apps, re-introducing
the device flow used by devices with limited user interfaces, additional
security enhancements for clients communicating with multiple service
providers, definition of claims used with JSON Web Tokens, techniques to
mitigate open redirector attacks, as well as guidance on encoding state
information.

For feedback and discussion about our specifications please
subscribe to our public mailing list at <oauth AT ietf.org>.

For security related bug reports that relate to our specifications
please contact <oauth-security-reports AT ietf.org>. If the reported
bug report turns out to be implementation-specific we will attempt
to forward it to the appropriate developers.

Milestones:


WG action announcement

From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: "The IESG" <iesg@ietf.org>,
    oauth-chairs@ietf.org,
    oauth@ietf.org 
Subject: WG Action: Rechartered Web Authorization Protocol (oauth)

The Web Authorization Protocol (oauth) WG in the Security Area of the
IETF has been rechartered. For additional information, please contact the
Area Directors or the WG Chairs.

Web Authorization Protocol (oauth)
-----------------------------------------------------------------------
Current status: Active WG

Chairs:
  Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
  Derek Atkins <derek@ihtfp.com>

Assigned Area Director:
  Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>

Mailing list:
  Address: oauth@ietf.org
  To subscribe: https://www.ietf.org/mailman/listinfo/oauth
  Archive: https://mailarchive.ietf.org/arch/browse/oauth/

Charter: https://datatracker.ietf.org/doc/charter-ietf-oauth/

The Web Authorization (OAuth) protocol allows a user to grant a
third-party web site or application access to the user's protected
resources, without necessarily revealing their long-term credentials,
or even their identity. For example, a photo-sharing site that
supports OAuth could allow its users to use a third-party printing web
site to print their private pictures, without allowing the printing
site to gain full control of the user's account and without having the
user share his or her photo-sharing sites' long-term credential with
the printing site.

The OAuth 2.0 protocol suite already includes

* a procedure for enabling a client to register with an authorization
  server,
* a protocol for obtaining authorization tokens from an authorization
  server with the resource owner's consent, and
* protocols for presenting these authorization tokens to protected
  resources for access to a resource.

This protocol suite has been enhanced with functionality for
interworking with legacy identity infrastructure (such as SAML), token
revocation, token exchange, dynamic client registration, token
introspection, a standardized token format with the JSON Web Token, and
specifications that mitigate security attacks, such as Proof Key for
Code Exchange.

The ongoing standardization efforts within the OAuth working group
focus on increasing interoperability of OAuth deployments and to
improve security. More specifically, the working group is defining proof
of possession tokens, developing a discovery mechanism, providing
guidance for the use of OAuth with native apps, re-introducing
the device flow used by devices with limited user interfaces, additional
security enhancements for clients communicating with multiple service
providers, definition of claims used with JSON Web Tokens, techniques to
mitigate open redirector attacks, as well as guidance on encoding state
information.

For feedback and discussion about our specifications please
subscribe to our public mailing list at <oauth AT ietf.org>.

For security related bug reports that relate to our specifications
please contact <oauth-security-reports AT ietf.org>. If the reported
bug report turns out to be implementation-specific we will attempt
to forward it to the appropriate developers.

Milestones:
  Feb 2016 - Submit 'Request by JWS ver.1.0 for OAuth 2.0' to the IESG
for consideration as a Proposed Standard
  Apr 2016 - Submit 'Proof-of-Possession OAuth Security' document bundle
for consideration as a Proposed Standard
  Jul 2016 - Submit 'OAuth 2.0 Token Exchange' to the IESG for
consideration as a Proposed Standard


Ballot announcement