draft-ietf-ace-oauth-params-09.txt   draft-ietf-ace-oauth-params-10.txt 
ACE Working Group L. Seitz ACE Working Group L. Seitz
Internet-Draft Combitech Internet-Draft Combitech
Intended status: Standards Track December 22, 2019 Intended status: Standards Track January 7, 2020
Expires: June 24, 2020 Expires: July 10, 2020
Additional OAuth Parameters for Authorization in Constrained Additional OAuth Parameters for Authorization in Constrained
Environments (ACE) Environments (ACE)
draft-ietf-ace-oauth-params-09 draft-ietf-ace-oauth-params-10
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 the framework for introspection endpoints when used with the framework for
authentication and authorization for constrained environments (ACE). authentication and authorization for constrained environments (ACE).
These are used to express the proof-of-possession key the client These are used to express the proof-of-possession key the client
wishes to use, the proof-of-possession key that the Authorization wishes to use, the proof-of-possession key that the Authorization
Server has selected, and the key the Resource Server should use to Server has selected, and the key the Resource Server should use to
authenticate to the client. authenticate to the client.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 June 24, 2020. This Internet-Draft will expire on July 10, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2020 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
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 27 skipping to change at page 2, line 27
4.1. AS-to-RS Response . . . . . . . . . . . . . . . . . . . . 6 4.1. AS-to-RS Response . . . . . . . . . . . . . . . . . . . . 6
5. Confirmation Method Parameters . . . . . . . . . . . . . . . 8 5. Confirmation Method Parameters . . . . . . . . . . . . . . . 8
6. CBOR Mappings . . . . . . . . . . . . . . . . . . . . . . . . 9 6. CBOR Mappings . . . . . . . . . . . . . . . . . . . . . . . . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 9 7. Security Considerations . . . . . . . . . . . . . . . . . . . 9
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 . . . . . . . . . . . . . . . . . . 9
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. OAuth Parameters CBOR Mappings Registraton . . . . . . . 11 9.5. OAuth Parameters CBOR Mappings Registraton . . . . . . . 10
9.6. OAuth Token Introspection Response CBOR Mappings 9.6. OAuth Token Introspection Response CBOR Mappings
Registration . . . . . . . . . . . . . . . . . . . . . . 11 Registration . . . . . . . . . . . . . . . . . . . . . . 11
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
11.1. Normative References . . . . . . . . . . . . . . . . . . 12 11.1. Normative References . . . . . . . . . . . . . . . . . . 11
11.2. Informative References . . . . . . . . . . . . . . . . . 13 11.2. Informative References . . . . . . . . . . . . . . . . . 13
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 13 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 13
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
parameters for interactions with the OAuth 2.0 [RFC6749] token and parameters for interactions with the OAuth 2.0 [RFC6749] token and
introspection endpoints, as well as some new claims to be used in introspection endpoints, as well as some new claims to be used in
access tokens. These parameters and claims can also be used in other access tokens. These parameters and claims can also be used in other
skipping to change at page 3, line 29 skipping to change at page 3, line 29
COSE_Key defined in section 7 of [RFC8152]. COSE_Key defined in section 7 of [RFC8152].
Note that the term "endpoint" is used here following its OAuth 2.0 Note that the term "endpoint" is used here following its OAuth 2.0
[RFC6749] definition, which is to denote resources such as token and [RFC6749] definition, which is to denote resources such as token and
introspection at the AS and authz-info at the RS. The CoAP [RFC7252] introspection at the AS and authz-info at the RS. The CoAP [RFC7252]
definition, which is "An entity participating in the CoAP protocol" definition, which is "An entity participating in the CoAP protocol"
is not used in this specification. is not used in this specification.
3. Parameters for the Token Endpoint 3. Parameters for the Token Endpoint
This section defines additional parameters for the interations with This section defines additional parameters for the interactions with
the token endpoint in the ACE framework [I-D.ietf-ace-oauth-authz]. the token endpoint in the ACE framework [I-D.ietf-ace-oauth-authz].
3.1. Client-to-AS Request 3.1. Client-to-AS Request
This section defines the "req_cnf" parameter allowing clients to This section defines the "req_cnf" parameter allowing clients to
request a specific proof-of-possession key in an access token from a request a specific proof-of-possession key in an access token from a
token endpoint in the ACE framework [I-D.ietf-ace-oauth-authz]: token endpoint in the ACE framework [I-D.ietf-ace-oauth-authz]:
req_cnf req_cnf
OPTIONAL. This field contains information about the key the OPTIONAL. This field contains information about the key the
client would like to bind to the access token for proof-of- client would like to bind to the access token for proof-of-
possession. It is RECOMMENDED that an AS reject a request possession. It is RECOMMENDED that an AS reject a request
containing a symmetric key value in the 'req_cnf' field containing a symmetric key value in the 'req_cnf' field
(kty=Symmetric), since the AS is expected to be able to generate (kty=Symmetric), since the AS is expected to be able to generate
better symmetric keys than a constrained client. The AS MUST better symmetric keys than a constrained client. The AS MUST
verify that the client really is in possession of the verify that the client really is in possession of the
corresponding key. Values of this parameter follow the syntax of corresponding key. Values of this parameter follow the syntax and
the "cnf" claim from section 3.1 of semantics of the "cnf" claim from section 3.1 of
[I-D.ietf-ace-cwt-proof-of-possession]. [I-D.ietf-ace-cwt-proof-of-possession].
Figure 1 shows a request for an access token using the "req_cnf" Figure 1 shows a request for an access token using the "req_cnf"
parameter to request a specific public key as proof-of-possession parameter to request a specific public key as proof-of-possession
key. The content is displayed in CBOR diagnostic notation, without key. The content is displayed in CBOR diagnostic notation, without
abbreviations and with line-breaks for better readability. abbreviations and with line-breaks for better readability.
Header: POST (Code=0.02) Header: POST (Code=0.02)
Uri-Host: "as.example.com" Uri-Host: "as.example.com"
Uri-Path: "token" Uri-Path: "token"
skipping to change at page 4, line 38 skipping to change at page 4, line 38
3.2. AS-to-Client Response 3.2. AS-to-Client Response
This section defines the following additional parameters for an AS This section defines the following additional parameters for an AS
response to a request to the token endpoint: response to a request to the token endpoint:
cnf cnf
REQUIRED if the token type is "pop" and a symmetric key is used. REQUIRED if the token type is "pop" and a symmetric key is used.
MAY be present for asymmetric proof-of-possession keys. This MAY be present for asymmetric proof-of-possession keys. This
field contains the proof-of-possession key that the AS selected field contains the proof-of-possession key that the AS selected
for the token. Values of this parameter follow the syntax of the for the token. Values of this parameter follow the syntax and
"cnf" claim from section 3.1 of semantics of the "cnf" claim from section 3.1 of
[I-D.ietf-ace-cwt-proof-of-possession]. See Section 5 for [I-D.ietf-ace-cwt-proof-of-possession]. See Section 5 for
additional discussion of the usage of this parameter. additional discussion of the usage of this parameter.
rs_cnf rs_cnf
OPTIONAL if the token type is "pop" and asymmetric keys are used. OPTIONAL if the token type is "pop" and asymmetric keys are used.
MUST NOT be present otherwise. This field contains information MUST NOT be present otherwise. This field contains information
about the public key used by the RS to authenticate. If this about the public key used by the RS to authenticate. If this
parameter is absent, either the RS does not use a public key or parameter is absent, either the RS does not use a public key or
the AS knows that the RS can authenticate itself to the client the AS knows that the RS can authenticate itself to the client
without additional information. Values of this parameter follow without additional information. Values of this parameter follow
the syntax of the "cnf" claim from section 3.1 of the syntax and semantics of the "cnf" claim from section 3.1 of
[I-D.ietf-ace-cwt-proof-of-possession]. See Section 5 for [I-D.ietf-ace-cwt-proof-of-possession]. See Section 5 for
additional discussion of the usage of this parameter. additional discussion of the usage of this parameter.
Figure 2 shows an AS response containing a token and a "cnf" Figure 2 shows an AS response containing a token and a "cnf"
parameter with a symmetric proof-of-possession key. parameter with a symmetric proof-of-possession key.
Header: Created (Code=2.01) Header: Created (Code=2.01)
Content-Format: "application/ace+cbor" Content-Format: "application/ace+cbor"
Payload: Payload:
skipping to change at page 6, line 36 skipping to change at page 6, line 36
3.3. The Resource Server Confirmation Claim 3.3. The Resource Server Confirmation Claim
If the AS needs to convey a hint to the RS about which key it should If the AS needs to convey a hint to the RS about which key it should
use to authenticate towards the client, this specification defines use to authenticate towards the client, this specification defines
the "rs_cnf" claim, which MAY be used in the access token, with the the "rs_cnf" claim, which MAY be used in the access token, with the
same syntax and semantics as defined in for the "rs_cnf" parameter. same syntax and semantics as defined in for the "rs_cnf" parameter.
4. Parameters for the Introspection Endpoint 4. Parameters for the Introspection Endpoint
This section defines additional parameters for the interations with This section defines an additional parameter for the interactions
the introspection endpoint in the ACE framework with the introspection endpoint in the ACE framework
[I-D.ietf-ace-oauth-authz]. [I-D.ietf-ace-oauth-authz].
4.1. AS-to-RS Response 4.1. AS-to-RS Response
This section defines the following additional parameters for an AS This section defines the following additional parameter for an AS
response to a request to the introspection endpoint: response to a request to the introspection endpoint:
cnf
OPTIONAL. This field contains information about the proof-of-
possession key that binds the client to the access token. Values
of this parameter follow the syntax of the "cnf" claim from
section 3.1 of [I-D.ietf-ace-cwt-proof-of-possession]. See
Section 5 for additional discussion of the usage of this
parameter.
rs_cnf rs_cnf
OPTIONAL. If the RS uses asymmetric keys to authenticate towards OPTIONAL. If the RS uses asymmetric keys to authenticate towards
the client (e.g., with a DTLS Raw Public Key handshake [RFC7250] the client (e.g., with a DTLS Raw Public Key handshake [RFC7250]
and it has several such keys (e.g., for different elliptic and it has several such keys (e.g., for different elliptic
curves), the AS can give the RS a hint using this parameter, as to curves), the AS can give the RS a hint using this parameter, as to
which key it should use. Values of this parameter follow the which key it should use. Values of this parameter follow the
syntax of the "cnf" claim from section 3.1 of syntax and semantics of the "cnf" claim from section 3.1 of
[I-D.ietf-ace-cwt-proof-of-possession]. See Section 5 for [I-D.ietf-ace-cwt-proof-of-possession]. See Section 5 for
additional discussion of the usage of this parameter. additional discussion of the usage of this parameter.
Furthermore the AS can use the "cnf" parameter specified in section
9.4 of [I-D.ietf-oauth-mtls] in an introspection response. For CBOR-
based interactions the AS MUST use the parameter mapping specified in
Figure 5.
Figure 4 shows an AS response to an introspection request including Figure 4 shows an AS response to an introspection request including
the "cnf" parameter to indicate the proof-of-possession key bound to the "cnf" parameter to indicate the proof-of-possession key bound to
the token and the "rs_cnf" parameter to indicate the key the RS is the token and the "rs_cnf" parameter to indicate the key the RS is
supposed to use to authenticate to the client. supposed to use to authenticate to the client.
Header: Created Code=2.01) Header: Created Code=2.01)
Content-Format: "application/ace+cbor" Content-Format: "application/ace+cbor"
Payload: Payload:
{ {
"active" : true, "active" : true,
skipping to change at page 10, line 36 skipping to change at page 10, line 36
o Change Controller: IESG o Change Controller: IESG
o Reference: Section 5 of [this document] o Reference: Section 5 of [this document]
o Name: "cnf" o Name: "cnf"
o Parameter Usage Location: token response o Parameter Usage Location: token response
o Change Controller: IESG o Change Controller: IESG
o Reference: Section 5 of [this document] o Reference: Section 5 of [this document]
9.4. OAuth Introspection Response Parameter Registration 9.4. OAuth Introspection Response Parameter Registration
This section registers the following parameters in the OAuth Token This section registers the following parameter in the OAuth Token
Introspection Response registry [IANA.TokenIntrospectionResponse]. Introspection Response registry [IANA.TokenIntrospectionResponse].
o Name: "cnf"
o Description: Key to prove the right to use a PoP token.
o Change Controller: IESG
o Reference: Section 4.1 of [this document]
o Name: "rs_cnf" o Name: "rs_cnf"
o Description: public key used by RS to authenticate itself to the o Description: public key used by RS to authenticate itself to the
client. client.
o Change Controller: IESG o Change Controller: IESG
o Reference: Section 4.1 of [this document] o Reference: Section 4.1 of [this document]
9.5. OAuth Parameters CBOR Mappings Registraton 9.5. OAuth Parameters CBOR Mappings Registraton
This section registers the following parameter mappings in the "OAuth This section registers the following parameter mappings in the "OAuth
Parameters CBOR Mappings" registry established in section 8.9. of Parameters CBOR Mappings" registry established in section 8.9. of
skipping to change at page 12, line 22 skipping to change at page 12, line 12
Web Tokens (CWTs)", draft-ietf-ace-cwt-proof-of- Web Tokens (CWTs)", draft-ietf-ace-cwt-proof-of-
possession-11 (work in progress), October 2019. possession-11 (work in progress), October 2019.
[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-29 Framework (ACE-OAuth)", draft-ietf-ace-oauth-authz-29
(work in progress), December 2019. (work in progress), December 2019.
[I-D.ietf-oauth-mtls]
Campbell, B., Bradley, J., Sakimura, N., and T.
Lodderstedt, "OAuth 2.0 Mutual-TLS Client Authentication
and Certificate-Bound Access Tokens", draft-ietf-oauth-
mtls-17 (work in progress), August 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>.
[IANA.OAuthParameters] [IANA.OAuthParameters]
 End of changes. 18 change blocks. 
32 lines changed or deleted 31 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/