JWT Response for OAuth Token Introspection
draft-ietf-oauth-jwt-introspection-response-08
| Document | Type | Active Internet-Draft (oauth WG) | |
|---|---|---|---|
| Last updated | 2019-09-25 (latest revision 2019-09-20) | ||
| Replaces | draft-lodderstedt-oauth-jwt-introspection-response | ||
| Stream | IETF | ||
| Intended RFC status | Proposed Standard | ||
| Formats | plain text xml pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Rifaat Shekh-Yusef | ||
| Shepherd write-up | Show (last changed 2019-06-03) | ||
| IESG | IESG state | IESG Evaluation::AD Followup | |
| Consensus Boilerplate | Yes | ||
| Telechat date |
Has 2 DISCUSSes. Needs one more YES or NO OBJECTION position to pass. |
||
| Responsible AD | Roman Danyliw | ||
| Send notices to | Rifaat Shekh-Yusef <rifaat.ietf@gmail.com> | ||
| IANA | IANA review state | IANA OK - Actions Needed | |
| IANA expert review state | Expert Reviews OK | ||
Open Authentication Protocol T. Lodderstedt, Ed.
Internet-Draft yes.com AG
Intended status: Standards Track V. Dzhuvinov
Expires: March 22, 2020 Connect2id Ltd.
Sep 19, 2019
JWT Response for OAuth Token Introspection
draft-ietf-oauth-jwt-introspection-response-08
Abstract
This specification proposes an additional JSON Web Token (JWT)
secured 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 March 22, 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 March 22, 2020 [Page 1]
Internet-Draft JWT Response Sep 2019
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Notation and Conventions . . . . . . . . . . . . 3
3. Resource server management . . . . . . . . . . . . . . . . . 3
4. Requesting a JWT Response . . . . . . . . . . . . . . . . . . 4
5. JWT Response . . . . . . . . . . . . . . . . . . . . . . . . 4
6. Client Metadata . . . . . . . . . . . . . . . . . . . . . . . 7
7. Authorization Server Metadata . . . . . . . . . . . . . . . . 8
8. Security Considerations . . . . . . . . . . . . . . . . . . . 9
8.1. Cross-JWT Confusion . . . . . . . . . . . . . . . . . . . 9
8.2. Token Data Leakage . . . . . . . . . . . . . . . . . . . 9
8.3. Keeping Token Data Confidential from OAuth Clients . . . 10
8.4. Logging and Audit of Introspection Activity . . . . . . . 10
9. Privacy Considerations . . . . . . . . . . . . . . . . . . . 10
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
11.1. OAuth Dynamic Client Registration Metadata Registration 11
11.1.1. Registry Contents . . . . . . . . . . . . . . . . . 11
11.2. OAuth Authorization Server Metadata Registration . . . . 12
11.2.1. Registry Contents . . . . . . . . . . . . . . . . . 12
11.3. Media Type Registration . . . . . . . . . . . . . . . . 12
11.3.1. Registry Contents . . . . . . . . . . . . . . . . . 13
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
12.1. Normative References . . . . . . . . . . . . . . . . . . 14
12.2. Informative References . . . . . . . . . . . . . . . . . 15
Appendix A. Document History . . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
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 enables deployments to implement opaque
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 token introspection response for
an access token, including cases where the authorization server
assumes liability for the content of the token introspection
response. An example is a resource server using verified person data
to create certificates, which in turn are used to create qualified
Show full document text