draft-ietf-oauth-resource-indicators-07.txt   draft-ietf-oauth-resource-indicators-08.txt 
OAuth Working Group B. Campbell OAuth Working Group B. Campbell
Internet-Draft Ping Identity Internet-Draft Ping Identity
Intended status: Standards Track J. Bradley Intended status: Standards Track J. Bradley
Expires: March 8, 2020 Yubico Expires: March 14, 2020 Yubico
H. Tschofenig H. Tschofenig
Arm Limited Arm Limited
September 5, 2019 September 11, 2019
Resource Indicators for OAuth 2.0 Resource Indicators for OAuth 2.0
draft-ietf-oauth-resource-indicators-07 draft-ietf-oauth-resource-indicators-08
Abstract Abstract
This document specifies an extension to the OAuth 2.0 Authorization This document specifies an extension to the OAuth 2.0 Authorization
Framework defining request parameters that enable a client to Framework defining request parameters that enable a client to
explicitly signal to an authorization server about the identity of explicitly signal to an authorization server about the identity of
the protected resource(s) to which it is requesting access. the protected resource(s) to which it is requesting access.
Status of This Memo Status of This Memo
skipping to change at page 1, line 36 skipping to change at page 1, line 36
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 8, 2020. This Internet-Draft will expire on March 14, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 25 skipping to change at page 2, line 25
3. Security Considerations . . . . . . . . . . . . . . . . . . . 9 3. Security Considerations . . . . . . . . . . . . . . . . . . . 9
4. Privacy Considerations . . . . . . . . . . . . . . . . . . . 10 4. Privacy Considerations . . . . . . . . . . . . . . . . . . . 10
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
5.1. OAuth Parameters Registration . . . . . . . . . . . . . . 10 5.1. OAuth Parameters Registration . . . . . . . . . . . . . . 10
5.2. OAuth Extensions Error Registration . . . . . . . . . . . 10 5.2. OAuth Extensions Error Registration . . . . . . . . . . . 10
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
6.1. Normative References . . . . . . . . . . . . . . . . . . 11 6.1. Normative References . . . . . . . . . . . . . . . . . . 11
6.2. Informative References . . . . . . . . . . . . . . . . . 11 6.2. Informative References . . . . . . . . . . . . . . . . . 11
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 12 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 12
Appendix B. Document History . . . . . . . . . . . . . . . . . . 12 Appendix B. Document History . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
Several years of deployment and implementation experience with the Several years of deployment and implementation experience with the
OAuth 2.0 Authorization Framework [RFC6749] has uncovered a need, in OAuth 2.0 Authorization Framework [RFC6749] has uncovered a need, in
some circumstances such as an authorization server servicing a some circumstances such as an authorization server servicing a
significant number of diverse resources, for the client to explicitly significant number of diverse resources, for the client to explicitly
signal to the authorization server where it intends to use the access signal to the authorization server where it intends to use the access
token it is requesting. token it is requesting.
skipping to change at page 4, line 12 skipping to change at page 4, line 12
In requests to the authorization server, a client MAY indicate the In requests to the authorization server, a client MAY indicate the
protected resource (a.k.a. resource server, application, API, etc.) protected resource (a.k.a. resource server, application, API, etc.)
to which it is requesting access by including the following parameter to which it is requesting access by including the following parameter
in the request. in the request.
resource resource
Indicates the target service or resource to which access is being Indicates the target service or resource to which access is being
requested. Its value MUST be an absolute URI, as specified by requested. Its value MUST be an absolute URI, as specified by
Section 4.3 of [RFC3986]. The URI MUST NOT include a fragment Section 4.3 of [RFC3986]. The URI MUST NOT include a fragment
component. It SHOULD NOT include a query component, but it is component. It SHOULD NOT include a query component, but it is
recognized that there are cases that make a query component recognized that there are cases that make a query component a
useful. The "resource" parameter URI value is an identifier useful and necessary part of the resource parameter, such as when
representing the identity of the resource, which MAY be a locator query parameter(s) are used to scope requests to an application.
that corresponds to a network addressable location where the The "resource" parameter URI value is an identifier representing
target resource is hosted. Multiple "resource" parameters MAY be the identity of the resource, which MAY be a locator that
used to indicate that the requested token is intended to be used corresponds to a network addressable location where the target
at multiple resources. resource is hosted. Multiple "resource" parameters MAY be used to
indicate that the requested token is intended to be used at
multiple resources.
The parameter value identifies a resource to which the client is The parameter value identifies a resource to which the client is
requesting access. The parameter can carry the location of a requesting access. The parameter can carry the location of a
protected resource, typically as an https URL, or a more abstract protected resource, typically as an https URL, or a more abstract
identifier. This enables the authorization server to apply policy as identifier. This enables the authorization server to apply policy as
appropriate for the resource, such as determining the type and appropriate for the resource, such as determining the type and
content of tokens to be issued, if and how tokens are encrypted, and content of tokens to be issued, if and how tokens are encrypted, and
applying appropriate audience restrictions. applying appropriate audience restrictions.
The client SHOULD provide the most specific URI that it can for the The client SHOULD provide the most specific URI that it can for the
skipping to change at page 12, line 27 skipping to change at page 12, line 27
Vittorio Bertocci, Sergey Beryozkin, Roman Danyliw, William Denniss, Vittorio Bertocci, Sergey Beryozkin, Roman Danyliw, William Denniss,
Vladimir Dzhuvinov, George Fletcher, Dick Hardt, Phil Hunt, Michael Vladimir Dzhuvinov, George Fletcher, Dick Hardt, Phil Hunt, Michael
Jones, Benjamin Kaduk, Barry Leiba, Torsten Lodderstedt, Anthony Jones, Benjamin Kaduk, Barry Leiba, Torsten Lodderstedt, Anthony
Nadalin, Justin Richer, Adam Roach, Nat Sakimura, Rifaat Shekh-Yusef, Nadalin, Justin Richer, Adam Roach, Nat Sakimura, Rifaat Shekh-Yusef,
Filip Skokan, Eric Vyncke, and Hans Zandbelt. Filip Skokan, Eric Vyncke, and Hans Zandbelt.
Appendix B. Document History Appendix B. Document History
[[ to be removed by the RFC Editor before publication as an RFC ]] [[ to be removed by the RFC Editor before publication as an RFC ]]
draft-ietf-oauth-resource-indicators-08
o One last update from IESG evaluation comments
(https://mailarchive.ietf.org/arch/msg/oauth/
x87EQ0Dwq3_ERrH5PzDjRSaWBt4).
draft-ietf-oauth-resource-indicators-07 draft-ietf-oauth-resource-indicators-07
o One more update from IESG evaluation comments o One more update from IESG evaluation comments
(https://mailarchive.ietf.org/arch/msg/oauth/ (https://mailarchive.ietf.org/arch/msg/oauth/
RS0UZSsguQurHl4P18Zo77BzZnU). RS0UZSsguQurHl4P18Zo77BzZnU).
draft-ietf-oauth-resource-indicators-06 draft-ietf-oauth-resource-indicators-06
o Expand JWT acronym on first use per Genart last call review. o Expand JWT acronym on first use per Genart last call review.
o Updates from IESG evaluation comments. o Updates from IESG evaluation comments.
skipping to change at page 12, line 48 skipping to change at page 13, line 5
draft-ietf-oauth-resource-indicators-05 draft-ietf-oauth-resource-indicators-05
o Remove specific mention of error_uri, which is rarely (if ever) o Remove specific mention of error_uri, which is rarely (if ever)
used and seems to only confuse things for readers of extensions used and seems to only confuse things for readers of extensions
like this one. like this one.
draft-ietf-oauth-resource-indicators-04 draft-ietf-oauth-resource-indicators-04
o Editorial updates from AD review that were overlooked in -03. o Editorial updates from AD review that were overlooked in -03.
draft-ietf-oauth-resource-indicators-03
o Editorial updates from AD review. o Editorial updates from AD review.
o Update draft-ietf-oauth-jwsreq ref to -19. o Update draft-ietf-oauth-jwsreq ref to -19.
o Update the IANA requests to say they update the registries. o Update the IANA requests to say they update the registries.
draft-ietf-oauth-resource-indicators-02
o Clarify that the value of the "resource" parameter is a URI which o Clarify that the value of the "resource" parameter is a URI which
can be an abstract identifier for the target resource and doesn't can be an abstract identifier for the target resource and doesn't
necessarily have to correspond to a network addressable location. necessarily have to correspond to a network addressable location.
draft-ietf-oauth-resource-indicators-01 draft-ietf-oauth-resource-indicators-01
o Significant rework of the main section of the document attempting o Significant rework of the main section of the document attempting
to clarify a number of things that came up at, around and after to clarify a number of things that came up at, around and after
IETF 102 and the call for adoption. IETF 102 and the call for adoption.
o Change the "invalid_resource" error to "invalid_target" to align o Change the "invalid_resource" error to "invalid_target" to align
 End of changes. 9 change blocks. 
14 lines changed or deleted 22 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/