JWT Response for OAuth Token Introspection
draft-ietf-oauth-jwt-introspection-response-04
Open Authentication Protocol T. Lodderstedt, Ed.
Internet-Draft yes.com AG
Intended status: Standards Track V. Dzhuvinov
Expires: January 23, 2020 Connect2id Ltd.
Jul 22, 2019
JWT Response for OAuth Token Introspection
draft-ietf-oauth-jwt-introspection-response-04
Abstract
This draft proposes an additional JSON Web Token (JWT) based response
for OAuth 2.0 Token Introspection.
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 January 23, 2020.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
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.
Lodderstedt & Dzhuvinov Expires January 23, 2020 [Page 1]
Internet-Draft JWT Response Jul 2019
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requesting a JWT Response . . . . . . . . . . . . . . . . . . 3
3. JWT Response . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Client Metadata . . . . . . . . . . . . . . . . . . . . . . . 4
5. Authorization Server Metadata . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6.1. Cross-JWT Confusion . . . . . . . . . . . . . . . . . . . 6
6.2. Token Data Leakage . . . . . . . . . . . . . . . . . . . 6
6.3. Data Minimization . . . . . . . . . . . . . . . . . . . . 7
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
8.1. OAuth Dynamic Client Registration Metadata Registration . 7
8.1.1. Registry Contents . . . . . . . . . . . . . . . . . . 7
8.2. OAuth Authorization Server Metadata Registration . . . . 8
8.2.1. Registry Contents . . . . . . . . . . . . . . . . . . 8
8.3. OAuth Token Introspection Response . . . . . . . . . . . 8
8.3.1. Registry Contents . . . . . . . . . . . . . . . . . . 9
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
9.1. Normative References . . . . . . . . . . . . . . . . . . 13
9.2. Informative References . . . . . . . . . . . . . . . . . 14
Appendix A. Document History . . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction
OAuth 2.0 Token Introspection [RFC7662] specifies a method for a
protected resource to query an OAuth 2.0 authorization server to
determine the state of an access token and obtain data associated
with the access token. This allows deployments to implement
identifier-based access tokens in an interoperable way.
The introspection response, as specified in OAuth 2.0 Token
Introspection [RFC7662], is a plain JSON object. However, there are
use cases where the resource server requires stronger assurance that
the authorization server issued the access token, including cases
where the authorization server assumes liability for the token's
content. An example is a resource server using verified person data
to create certificates, which in turn are used to create qualified
electronic signatures.
In such use cases it may be useful or even required to return a
signed JWT as the introspection response. This specification extends
the token introspection endpoint with the capability to return
responses as JWTs.
Lodderstedt & Dzhuvinov Expires January 23, 2020 [Page 2]
Internet-Draft JWT Response Jul 2019
Show full document text