draft-ietf-oauth-resource-indicators-06.txt   draft-ietf-oauth-resource-indicators-07.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 8, 2020 Yubico
H. Tschofenig H. Tschofenig
Arm Limited Arm Limited
September 5, 2019 September 5, 2019
Resource Indicators for OAuth 2.0 Resource Indicators for OAuth 2.0
draft-ietf-oauth-resource-indicators-06 draft-ietf-oauth-resource-indicators-07
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 4, line 10 skipping to change at page 4, line 10
2. Resource Parameter 2. Resource Parameter
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], which MAY include a query component but Section 4.3 of [RFC3986]. The URI MUST NOT include a fragment
MUST NOT include a fragment component. The "resource" parameter component. It SHOULD NOT include a query component, but it is
URI value is an identifier representing the identity of the recognized that there are cases that make a query component
resource, which MAY be a locator that corresponds to a network useful. The "resource" parameter URI value is an identifier
addressable location where the target resource is hosted. representing the identity of the resource, which MAY be a locator
Multiple "resource" parameters MAY be used to indicate that the that corresponds to a network addressable location where the
requested token is intended to be used at multiple resources. target 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-07
o One more update from IESG evaluation comments
(https://mailarchive.ietf.org/arch/msg/oauth/
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.
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.
skipping to change at page 12, line 48 skipping to change at page 13, line 5
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 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
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
with draft-ietf-oauth-token-exchange, which has some overlap in with draft-ietf-oauth-token-exchange, which has some overlap in
functionality. functionality.
o Allow the "resource" parameter value to have a query component o Allow the "resource" parameter value to have a query component
(aligning with draft-ietf-oauth-token-exchange). (aligning with draft-ietf-oauth-token-exchange).
o Moved the Security Considerations section to before the IANA o Moved the Security Considerations section to before the IANA
Considerations. Considerations.
 End of changes. 5 change blocks. 
10 lines changed or deleted 18 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/