JWT Response for OAuth Token Introspection
draft-lodderstedt-oauth-jwt-introspection-response-01

Document Type Active Internet-Draft (individual)
Last updated 2018-05-28
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Open Authentication Protocol                         T. Lodderstedt, Ed.
Internet-Draft                                                YES.com AG
Intended status: Standards Track                            V. Dzhuvinov
Expires: November 29, 2018                               Connect2id Ltd.
                                                            May 28, 2018

               JWT Response for OAuth Token Introspection
         draft-lodderstedt-oauth-jwt-introspection-response-01

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 November 29, 2018.

Copyright Notice

   Copyright (c) 2018 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 November 29, 2018               [Page 1]
Internet-Draft                JWT Response                      May 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requesting a JWT Response . . . . . . . . . . . . . . . . . .   2
   3.  JWT Response  . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Client Metadata . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Authorization Server Metadata . . . . . . . . . . . . . . . .   5
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     7.1.  OAuth Dynamic Client Registration Metadata Registration .   5
       7.1.1.  Registry Contents . . . . . . . . . . . . . . . . . .   5
     7.2.  OAuth Authorization Server Metadata Registration  . . . .   6
       7.2.1.  Registry Contents . . . . . . . . . . . . . . . . . .   6
     7.3.  OAuth Token Introspection Response  . . . . . . . . . . .   7
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
     8.1.  Cross-JWT Confusion . . . . . . . . . . . . . . . . . . .   7
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Appendix A.  Document History . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

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 authorisation server issued the access token, including cases
   where the authorisation server assumes liability for the token's
   content.  An example is a resource server using verified person data
   to create qualified electronic signatures.

   In such use cases, it would be useful to return a signed JWT as the
   introspection response.  This specification extends the Token
   Introspection endpoint with the capability to return responses as
   JWTs.

2.  Requesting a JWT Response

   A resource server requests to receive a JWT introspection response by
   including an Accept header with content type "application/jwt" in the
   introspection request.

Lodderstedt & Dzhuvinov Expires November 29, 2018               [Page 2]
Internet-Draft                JWT Response                      May 2018

   The following is a non-normative example request:
Show full document text