OAuth 2.0 Demonstration of Proof-of-Possession at the Application Layer (DPoP)
draft-ietf-oauth-dpop-01
Web Authorization Protocol D. Fett
Internet-Draft yes.com
Intended status: Standards Track B. Campbell
Expires: 2 November 2020 Ping Identity
J. Bradley
Yubico
T. Lodderstedt
yes.com
M. Jones
Microsoft
D. Waite
Ping Identity
1 May 2020
OAuth 2.0 Demonstration of Proof-of-Possession at the Application Layer
(DPoP)
draft-ietf-oauth-dpop-01
Abstract
This document describes a mechanism for sender-constraining OAuth 2.0
tokens via a proof-of-possession mechanism on the application level.
This mechanism allows for the detection of replay attacks with access
and refresh tokens.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 2 November 2020.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
Fett, et al. Expires 2 November 2020 [Page 1]
Internet-Draft OAuth DPoP May 2020
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License text
as described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions and Terminology . . . . . . . . . . . . . . . 3
2. Main Objective . . . . . . . . . . . . . . . . . . . . . . . 4
3. Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. DPoP Proof JWTs . . . . . . . . . . . . . . . . . . . . . . . 6
4.1. DPoP Proof JWT Syntax . . . . . . . . . . . . . . . . . . 6
4.2. Checking DPoP Proofs . . . . . . . . . . . . . . . . . . 7
5. Token Request (Binding Tokens to a Public Key) . . . . . . . 8
6. Resource Access (Proof of Possession for Access Tokens) . . . 9
7. Public Key Confirmation . . . . . . . . . . . . . . . . . . . 11
8. Authorization Server Metadata . . . . . . . . . . . . . . . . 12
9. Security Considerations . . . . . . . . . . . . . . . . . . . 12
9.1. DPoP Proof Replay . . . . . . . . . . . . . . . . . . . . 13
9.2. Signed JWT Swapping . . . . . . . . . . . . . . . . . . . 13
9.3. Signature Algorithms . . . . . . . . . . . . . . . . . . 13
9.4. Message Integrity . . . . . . . . . . . . . . . . . . . . 13
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
10.1. OAuth Access Token Type Registration . . . . . . . . . . 14
10.2. HTTP Authentication Scheme Registration . . . . . . . . 14
10.3. Media Type Registration . . . . . . . . . . . . . . . . 14
10.4. JWT Confirmation Methods Registration . . . . . . . . . 15
10.5. JSON Web Token Claims Registration . . . . . . . . . . . 15
10.6. HTTP Message Header Field Names Registration . . . . . . 15
10.7. Authorization Server Metadata Registration . . . . . . . 16
11. Normative References . . . . . . . . . . . . . . . . . . . . 16
12. Informative References . . . . . . . . . . . . . . . . . . . 17
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 19
Appendix B. Document History . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21
Show full document text