|Can you please add another item to the Agenda of the Wednesday session? I just created a new draft, which adds a JWT-based response mode to the OAuth Token Introspection Endpoint (see attachment). I would like to present this topic to the working group. 10 min should be enough. |
I will submit the draft as soon as the submission tool re-opens.
|Open Authentication Protocol||T. Lodderstedt, Ed.|
|Intended status: Standards Track||March 11, 2018|
|Expires: September 10, 2018|
JWT Response for OAuth Token Introspection
This draft proposes an additional JWT-based response type for the OAuth 2.0 Token Introspection endpoint.
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 http://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 September 10, 2018.
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 (http://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.
- 1. Introduction
- 2. JWT Response
- 3. Client Metadata
- 4. Acknowledgements
- 5. IANA Considerations
- 6. Security Considerations
- 7. References
- Author's Address
OAuth 2.0 Token Introspection [RFC7662] introduces a mechanisms to query data associated with a certain access token and its status at the respective authorization server. This allows deployments to implement handle-based access tokens in an interoperable way.
The introspection endpoint as specified in OAuth 2.0 Token Introspection [RFC7662] returns the token data as a plain JSON object in "application/json" format. However, there are use cases where the resource server needs evidence about the fact the AS minted the access token and is liable for its contents. 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 introspection response. This draft extends the Introspection Endpoint by the capability to return responses as JWTs.
The introspection endpoint may respond with a JWT in "application/jwt" format.
This JWT may contain all the members describes in Section 2.2. of [RFC7662].
TBD: is the status needed in this format?
The authorization server determines what format to use for a particular introspection response. The decision can be based on the mechanisms described in this section.
The proposal is to register resource servers as client and let them determine the response format by utilizing new parameters for dynamic client registration.
The new parameters follow the pattern established by the OpenID Connect Dynamic Client registration [OpenID.Registration] specification for configuring signing and encryption algorithms for the user info endpoint.
The following parameters are introduced by this specification:
- JWS [RFC7515] alg algorithm JWA [RFC7518] REQUIRED for signing introspection responses. If this is specified, the response will be JWT [RFC7519] serialized, and signed using JWS. The default, if omitted, is for the introspection response to return the Claims as a UTF-8 encoded JSON object using the application/json content-type as defined in [RFC7662].
- JWE [RFC7516] alg algorithm JWA [RFC7518] REQUIRED for encrypting introspection responses. If both signing and encryption are requested, the response will be signed then encrypted, with the result being a Nested JWT, as defined in JWT [RFC7519]. The default, if omitted, is that no encryption is performed.
- JWE [RFC7516] enc algorithm JWA [RFC7518] REQUIRED for encrypting introspection responses. If introspection_response_encrypted_response_algy is specified, the default for this value is A128CBC-HS256. When introspection_response_encrypted_response_enc is included, introspection_response_encrypted_response_alg MUST also be provided.
We would like to thank ...
|[RFC2119]||Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997.|
|[RFC2246]||Dierks, T. and C. Allen, "The TLS Protocol Version 1.0", RFC 2246, DOI 10.17487/RFC2246, January 1999.|
|[RFC7519]||Jones, M., Bradley, J. and N. Sakimura, "JSON Web Token (JWT)", RFC 7519, DOI 10.17487/RFC7519, May 2015.|
|[RFC7591]||Richer, J., Jones, M., Bradley, J., Machulak, M. and P. Hunt, "OAuth 2.0 Dynamic Client Registration Protocol", RFC 7591, DOI 10.17487/RFC7591, July 2015.|
|[RFC7662]||Richer, J., "OAuth 2.0 Token Introspection", RFC 7662, DOI 10.17487/RFC7662, October 2015.|
|[RFC7518]||Jones, M., "JSON Web Algorithms (JWA)", RFC 7518, DOI 10.17487/RFC7518, May 2015.|
|[RFC7515]||Jones, M., Bradley, J. and N. Sakimura, "JSON Web Signature (JWS)", RFC 7515, DOI 10.17487/RFC7515, May 2015.|
|[RFC7516]||Jones, M. and J. Hildebrand, "JSON Web Encryption (JWE)", RFC 7516, DOI 10.17487/RFC7516, May 2015.|
|[OpenID.Registration]||NRIPing IdentityMicrosoft, "OpenID Connect Dynamic Client Registration 1.0 incorporating errata set 1", Nov 2014.|
Description: S/MIME cryptographic signature
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth