draft-ietf-ace-oauth-params-01.txt   draft-ietf-ace-oauth-params-02.txt 
ACE Working Group L. Seitz ACE Working Group L. Seitz
Internet-Draft RISE Internet-Draft RISE
Intended status: Standards Track November 26, 2018 Intended status: Standards Track January 29, 2019
Expires: May 30, 2019 Expires: August 2, 2019
Additional OAuth Parameters for Authorization in Constrained Additional OAuth Parameters for Authorization in Constrained
Environments (ACE) Environments (ACE)
draft-ietf-ace-oauth-params-01 draft-ietf-ace-oauth-params-02
Abstract Abstract
This specification defines new parameters for the OAuth 2.0 token and This specification defines new parameters for the OAuth 2.0 token and
introspection endpoints when used with framework for authentication introspection endpoints when used with the framework for
and authorization for constrained environments (ACE). These are used authentication and authorization for constrained environments (ACE).
to express the desired audience of a requested access token, the These are used to express the desired audience of a requested access
desired proof-of-possession key, the proof-of-possession key that the token, the desired proof-of-possession key, the proof-of-possession
AS has selected, and the key the RS should use to authenticate to the key that the AS has selected, and the key the RS should use to
client. authenticate to the client.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 May 30, 2019. This Internet-Draft will expire on August 2, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 24 skipping to change at page 2, line 24
3.2. AS-to-Client Response . . . . . . . . . . . . . . . . . . 4 3.2. AS-to-Client Response . . . . . . . . . . . . . . . . . . 4
3.3. The Resource Server Confirmation Claim . . . . . . . . . 6 3.3. The Resource Server Confirmation Claim . . . . . . . . . 6
4. Parameters for the Introspection Endpoint . . . . . . . . . . 6 4. Parameters for the Introspection Endpoint . . . . . . . . . . 6
4.1. AS-to-RS Response . . . . . . . . . . . . . . . . . . . . 6 4.1. AS-to-RS Response . . . . . . . . . . . . . . . . . . . . 6
5. Confirmation Method Parameters . . . . . . . . . . . . . . . 7 5. Confirmation Method Parameters . . . . . . . . . . . . . . . 7
6. CBOR Mappings . . . . . . . . . . . . . . . . . . . . . . . . 8 6. CBOR Mappings . . . . . . . . . . . . . . . . . . . . . . . . 8
7. Security Considerations . . . . . . . . . . . . . . . . . . . 8 7. Security Considerations . . . . . . . . . . . . . . . . . . . 8
8. Privacy Considerations . . . . . . . . . . . . . . . . . . . 9 8. Privacy Considerations . . . . . . . . . . . . . . . . . . . 9
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
9.1. JSON Web Token Claims . . . . . . . . . . . . . . . . . . 9 9.1. JSON Web Token Claims . . . . . . . . . . . . . . . . . . 9
9.2. CBOR Web Token Claims . . . . . . . . . . . . . . . . . . 9 9.2. CBOR Web Token Claims . . . . . . . . . . . . . . . . . . 10
9.3. OAuth Parameter Registration . . . . . . . . . . . . . . 10 9.3. OAuth Parameter Registration . . . . . . . . . . . . . . 10
9.4. OAuth Introspection Response Parameter Registration . . . 10 9.4. OAuth Introspection Response Parameter Registration . . . 10
9.5. Token Endpoint CBOR Mappings Registraton . . . . . . . . 11 9.5. Token Endpoint CBOR Mappings Registraton . . . . . . . . 11
9.6. Introspection Endpoint CBOR Mappings Registraton . . . . 11 9.6. Introspection Endpoint CBOR Mappings Registraton . . . . 11
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
11.1. Normative References . . . . . . . . . . . . . . . . . . 12 11.1. Normative References . . . . . . . . . . . . . . . . . . 12
11.2. Informative References . . . . . . . . . . . . . . . . . 13 11.2. Informative References . . . . . . . . . . . . . . . . . 13
Appendix A. Overlap with OAuth work . . . . . . . . . . . . . . 13 Appendix A. Overlap with OAuth work . . . . . . . . . . . . . . 13
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 14 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
The Authentication and Authorization for Constrained Environments The Authentication and Authorization for Constrained Environments
(ACE) specification [I-D.ietf-ace-oauth-authz] requires some new (ACE) specification [I-D.ietf-ace-oauth-authz] requires some new
skipping to change at page 9, line 25 skipping to change at page 9, line 25
group identifier to individual RS has to be provisioned to each RS group identifier to individual RS has to be provisioned to each RS
before the group-audience is usable. Managing dynamic groups could before the group-audience is usable. Managing dynamic groups could
be an issue, if the RS is not always reachable when the group be an issue, if the RS is not always reachable when the group
memberships change. Furthermore issuing access tokens bound to memberships change. Furthermore issuing access tokens bound to
symmetric proof-of-possession keys that apply to a group-audience is symmetric proof-of-possession keys that apply to a group-audience is
problematic, as an RS that is in possession of the access token can problematic, as an RS that is in possession of the access token can
impersonate the client towards the other RSs that are part of the impersonate the client towards the other RSs that are part of the
group. It is therefore NOT RECOMMENDED to issue access tokens bound group. It is therefore NOT RECOMMENDED to issue access tokens bound
to a group audience and symmetric proof-of possession keys. to a group audience and symmetric proof-of possession keys.
Even the client must be able to determine the correct values to put
into the "req_aud" parameter, in order to obtain a token for the
intended RS. Errors in this process can lead to the client
inadvertantly communicating with the wrong RS. The correct values
for "req_aud" can either be provisioned to the client as part of its
configuration, or dynamically looked up by the client in some
directory. In the latter case the integrity and correctness of the
directory data must be assured.
8. Privacy Considerations 8. Privacy Considerations
This document is an extension to [I-D.ietf-ace-oauth-authz]. All This document is an extension to [I-D.ietf-ace-oauth-authz]. All
privacy considerations from that document apply here as well. privacy considerations from that document apply here as well.
9. IANA Considerations 9. IANA Considerations
9.1. JSON Web Token Claims 9.1. JSON Web Token Claims
This specification registers the following new claim in the JSON Web This specification registers the following new claim in the JSON Web
skipping to change at page 10, line 4 skipping to change at page 10, line 13
o Reference: Section 3.3 of [this document] o Reference: Section 3.3 of [this document]
9.2. CBOR Web Token Claims 9.2. CBOR Web Token Claims
This specification registers the following new claim in the "CBOR Web This specification registers the following new claim in the "CBOR Web
Token (CWT) Claims" registry [IANA.CborWebTokenClaims]. Token (CWT) Claims" registry [IANA.CborWebTokenClaims].
o Claim Name: "rs_cnf" o Claim Name: "rs_cnf"
o Claim Description: The public key the RS is supposed to use to o Claim Description: The public key the RS is supposed to use to
authenticate to the client wielding this token. authenticate to the client wielding this token.
o JWT Claim Name: N/A o JWT Claim Name: N/A
o Claim Key: TBD (suggested: 39) o Claim Key: TBD (suggested: 40)
o Claim Value Type(s): map o Claim Value Type(s): map
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 3.3 of [this document] o Specification Document(s): Section 3.3 of [this document]
9.3. OAuth Parameter Registration 9.3. OAuth Parameter Registration
This section registers the following parameters in the "OAuth This section registers the following parameters in the "OAuth
Parameters" registry [IANA.OAuthParameters]: Parameters" registry [IANA.OAuthParameters]:
o Name: "req_aud" o Name: "req_aud"
skipping to change at page 12, line 19 skipping to change at page 12, line 26
[I-D.ietf-ace-cwt-proof-of-possession] [I-D.ietf-ace-cwt-proof-of-possession]
Jones, M., Seitz, L., Selander, G., Erdtman, S., and H. Jones, M., Seitz, L., Selander, G., Erdtman, S., and H.
Tschofenig, "Proof-of-Possession Key Semantics for CBOR Tschofenig, "Proof-of-Possession Key Semantics for CBOR
Web Tokens (CWTs)", draft-ietf-ace-cwt-proof-of- Web Tokens (CWTs)", draft-ietf-ace-cwt-proof-of-
possession-05 (work in progress), November 2018. possession-05 (work in progress), November 2018.
[I-D.ietf-ace-oauth-authz] [I-D.ietf-ace-oauth-authz]
Seitz, L., Selander, G., Wahlstroem, E., Erdtman, S., and Seitz, L., Selander, G., Wahlstroem, E., Erdtman, S., and
H. Tschofenig, "Authentication and Authorization for H. Tschofenig, "Authentication and Authorization for
Constrained Environments (ACE) using the OAuth 2.0 Constrained Environments (ACE) using the OAuth 2.0
Framework (ACE-OAuth)", draft-ietf-ace-oauth-authz-16 Framework (ACE-OAuth)", draft-ietf-ace-oauth-authz-18
(work in progress), October 2018. (work in progress), January 2019.
[IANA.CborWebTokenClaims] [IANA.CborWebTokenClaims]
IANA, "CBOR Web Token (CWT) Claims", IANA, "CBOR Web Token (CWT) Claims",
<https://www.iana.org/assignments/cwt/cwt.xhtml#claims- <https://www.iana.org/assignments/cwt/cwt.xhtml#claims-
registry>. registry>.
[IANA.JsonWebTokenClaims] [IANA.JsonWebTokenClaims]
IANA, "JSON Web Token Claims", IANA, "JSON Web Token Claims",
<https://www.iana.org/assignments/jwt/jwt.xhtml#claims>. <https://www.iana.org/assignments/jwt/jwt.xhtml#claims>.
skipping to change at page 13, line 34 skipping to change at page 13, line 38
[I-D.ietf-oauth-pop-key-distribution] [I-D.ietf-oauth-pop-key-distribution]
Bradley, J., Hunt, P., Jones, M., Tschofenig, H., and M. Bradley, J., Hunt, P., Jones, M., Tschofenig, H., and M.
Mihaly, "OAuth 2.0 Proof-of-Possession: Authorization Mihaly, "OAuth 2.0 Proof-of-Possession: Authorization
Server to Client Key Distribution", draft-ietf-oauth-pop- Server to Client Key Distribution", draft-ietf-oauth-pop-
key-distribution-04 (work in progress), October 2018. key-distribution-04 (work in progress), October 2018.
[I-D.ietf-oauth-resource-indicators] [I-D.ietf-oauth-resource-indicators]
Campbell, B., Bradley, J., and H. Tschofenig, "Resource Campbell, B., Bradley, J., and H. Tschofenig, "Resource
Indicators for OAuth 2.0", draft-ietf-oauth-resource- Indicators for OAuth 2.0", draft-ietf-oauth-resource-
indicators-01 (work in progress), October 2018. indicators-02 (work in progress), January 2019.
[RFC7519] Jones, M., Bradley, J., and N. Sakimura, "JSON Web Token [RFC7519] Jones, M., Bradley, J., and N. Sakimura, "JSON Web Token
(JWT)", RFC 7519, DOI 10.17487/RFC7519, May 2015, (JWT)", RFC 7519, DOI 10.17487/RFC7519, May 2015,
<https://www.rfc-editor.org/info/rfc7519>. <https://www.rfc-editor.org/info/rfc7519>.
Appendix A. Overlap with OAuth work Appendix A. Overlap with OAuth work
This document overlaps with draft work from OAuth, namely This document overlaps with draft work from OAuth, namely
[I-D.ietf-oauth-pop-key-distribution] and [I-D.ietf-oauth-pop-key-distribution] and
[I-D.ietf-oauth-resource-indicators]. [I-D.ietf-oauth-resource-indicators].
 End of changes. 12 change blocks. 
18 lines changed or deleted 26 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/