OAuth 2.0 Protected Resource Metadata
draft-jones-oauth-resource-metadata-01
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-01-19
|
|
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)
|
OAuth Working Group M. Jones
Internet-Draft Microsoft
Intended status: Standards Track P. Hunt
Expires: July 23, 2017 Oracle
January 19, 2017
OAuth 2.0 Protected Resource Metadata
draft-jones-oauth-resource-metadata-01
Abstract
This specification defines a metadata format that an OAuth 2.0 client
can use to obtain the information needed to interact with an OAuth
2.0 protected resource.
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 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 July 23, 2017.
Copyright Notice
Copyright (c) 2017 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.
Jones & Hunt Expires July 23, 2017 [Page 1]
Internet-Draft OAuth 2.0 Protected Resource Metadata January 2017
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Notation and Conventions . . . . . . . . . . 3
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. Protected Resource Metadata . . . . . . . . . . . . . . . . . 4
2.1. Signed Protected Resource Metadata . . . . . . . . . . . 5
3. Obtaining Protected Resource Metadata . . . . . . . . . . . . 6
3.1. Protected Resource Metadata Request . . . . . . . . . . . 6
3.2. Protected Resource Metadata Response . . . . . . . . . . 7
3.3. Protected Resource Metadata Validation . . . . . . . . . 8
4. Authorization Server Metadata . . . . . . . . . . . . . . . . 8
5. String Operations . . . . . . . . . . . . . . . . . . . . . . 8
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
6.1. TLS Requirements . . . . . . . . . . . . . . . . . . . . 9
6.2. Impersonation Attacks . . . . . . . . . . . . . . . . . . 9
6.3. Publishing Metadata in a Standard Format . . . . . . . . 10
6.4. Authorization Servers . . . . . . . . . . . . . . . . . . 10
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
7.1. OAuth Protected Resource Metadata Registry . . . . . . . 11
7.1.1. Registration Template . . . . . . . . . . . . . . . . 12
7.1.2. Initial Registry Contents . . . . . . . . . . . . . . 12
7.2. OAuth Authorization Server Metadata Registry . . . . . . 14
7.2.1. Registry Contents . . . . . . . . . . . . . . . . . . 14
7.3. Well-Known URI Registry . . . . . . . . . . . . . . . . . 14
7.3.1. Registry Contents . . . . . . . . . . . . . . . . . . 14
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
8.1. Normative References . . . . . . . . . . . . . . . . . . 14
8.2. Informative References . . . . . . . . . . . . . . . . . 16
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 17
Appendix B. Document History . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction
This specification defines a metadata format enabling OAuth 2.0
clients to obtain information needed to interact with an OAuth 2.0
protected resource. This specification is intentionally as parallel
as possible to "OAuth 2.0 Dynamic Client Registration Protocol"
[RFC7591], which enables a client to provide metadata about itself to
Show full document text