draft-ietf-oauth-discovery-00.txt   draft-ietf-oauth-discovery-01.txt 
OAuth Working Group M. Jones OAuth Working Group M. Jones
Internet-Draft Microsoft Internet-Draft Microsoft
Intended status: Standards Track N. Sakimura Intended status: Standards Track N. Sakimura
Expires: August 11, 2016 NRI Expires: August 20, 2016 NRI
J. Bradley J. Bradley
Ping Identity Ping Identity
February 8, 2016 February 17, 2016
OAuth 2.0 Discovery OAuth 2.0 Discovery
draft-ietf-oauth-discovery-00 draft-ietf-oauth-discovery-01
Abstract Abstract
This specification defines a mechanism for an OAuth 2.0 client to This specification defines a discovery metadata format that an OAuth
discover the resource owner's OAuth 2.0 authorization server and 2.0 client can use to obtain the information needed to interact with
obtain information needed to interact with it, including its OAuth an OAuth 2.0 authorization server, including its endpoint locations
2.0 endpoint locations and authorization server capabilities. and authorization server capabilities.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 11, 2016. This Internet-Draft will expire on August 20, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 12 skipping to change at page 2, line 12
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Notation and Conventions . . . . . . . . . . 3 1.1. Requirements Notation and Conventions . . . . . . . . . . 3
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. Authorization Server WebFinger Discovery . . . . . . . . . . . 4 2. Authorization Server Metadata . . . . . . . . . . . . . . . . 4
3. Authorization Server Metadata . . . . . . . . . . . . . . . . 6 3. Obtaining Authorization Server Discovery Metadata . . . . . . 7
4. Obtaining Authorization Server Configuration Information . . . 10 3.1. Authorization Server Discovery Metadata Request . . . . . 8
4.1. Authorization Server Configuration Information Request . . 10 3.2. Authorization Server Discovery Metadata Response . . . . . 8
4.2. Authorization Server Configuration Information Response . 11 3.3. Authorization Server Discovery Metadata Validation . . . . 9
4.3. Authorization Server Configuration Information 4. String Operations . . . . . . . . . . . . . . . . . . . . . . 10
Validation . . . . . . . . . . . . . . . . . . . . . . . . 12 5. Compatibility Notes . . . . . . . . . . . . . . . . . . . . . 10
5. String Operations . . . . . . . . . . . . . . . . . . . . . . 12 6. Security Considerations . . . . . . . . . . . . . . . . . . . 10
6. Compatibility Notes . . . . . . . . . . . . . . . . . . . . . 13 6.1. TLS Requirements . . . . . . . . . . . . . . . . . . . . . 10
7. Security Considerations . . . . . . . . . . . . . . . . . . . 13 6.2. Impersonation Attacks . . . . . . . . . . . . . . . . . . 11
7.1. TLS Requirements . . . . . . . . . . . . . . . . . . . . . 13 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
7.2. Impersonation Attacks . . . . . . . . . . . . . . . . . . 14 7.1. OAuth Discovery Metadata Registry . . . . . . . . . . . . 12
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 7.1.1. Registration Template . . . . . . . . . . . . . . . . 12
8.1. OAuth Discovery Metadata Registry . . . . . . . . . . . . 15 7.1.2. Initial Registry Contents . . . . . . . . . . . . . . 13
8.1.1. Registration Template . . . . . . . . . . . . . . . . 15 7.2. Updated Registration Instructions . . . . . . . . . . . . 16
8.1.2. Initial Registry Contents . . . . . . . . . . . . . . 16 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
8.2. Updated Registration Instructions . . . . . . . . . . . . 19 8.1. Normative References . . . . . . . . . . . . . . . . . . . 17
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 8.2. Informative References . . . . . . . . . . . . . . . . . . 19
9.1. Normative References . . . . . . . . . . . . . . . . . . . 19 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 20
9.2. Informative References . . . . . . . . . . . . . . . . . . 22 Appendix B. Document History . . . . . . . . . . . . . . . . . . 20
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20
Appendix B. Document History . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23
1. Introduction 1. Introduction
This specification generalizes the discovery mechanisms defined by This specification generalizes the discovery metadata format defined
"OpenID Connect Discovery 1.0" [OpenID.Discovery] in a way that is by "OpenID Connect Discovery 1.0" [OpenID.Discovery] in a way that is
compatible with OpenID Connect Discovery, while being applicable to a compatible with OpenID Connect Discovery, while being applicable to a
wider set of OAuth 2.0 use cases. This is intentionally parallel to wider set of OAuth 2.0 use cases. This is intentionally parallel to
the way that the "OAuth 2.0 Dynamic Client Registration Protocol" the way that the "OAuth 2.0 Dynamic Client Registration Protocol"
[RFC7591] specification generalized the dynamic client registration [RFC7591] specification generalized the dynamic client registration
mechanisms defined by "OpenID Connect Dynamic Client Registration mechanisms defined by "OpenID Connect Dynamic Client Registration
1.0" [OpenID.Registration] in a way that was compatible with it. 1.0" [OpenID.Registration] in a way that was compatible with it.
In order for an OAuth client to utilize OAuth 2.0 services for a The discovery metadata for an authorization server is retrieved from
resource owner, the client needs to know where the OAuth 2.0 a well-known location as a JSON [RFC7159] document, which declares
authorization server is. This specification uses WebFinger [RFC7033] its endpoint locations and authorization server capabilities. This
to locate the authorization server for an resource owner. This process is described in Section 3.
process is described in Section 2.
Once the authorization server has been identified, the configuration The means by which the client obtains the location of the
information for that authorization server is retrieved from a well- authorization server discovery metadata document is out of scope. In
known location as a JSON [RFC7159] document, including its OAuth 2.0 some cases, the location may be manually configured into the client.
endpoint locations and authorization server capabilities. This In other cases, it may be dynamically discovered, for instance,
process is described in Section 4. through the use of WebFinger [RFC7033], as described in Section 2 of
"OpenID Connect Discovery 1.0" [OpenID.Discovery].
1.1. Requirements Notation and Conventions 1.1. Requirements Notation and Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in RFC "OPTIONAL" in this document are to be interpreted as described in RFC
2119 [RFC2119]. 2119 [RFC2119].
All uses of JSON Web Signature (JWS) [JWS] and JSON Web Encryption All uses of JSON Web Signature (JWS) [JWS] and JSON Web Encryption
(JWE) [JWE] data structures in this specification utilize the JWS (JWE) [JWE] data structures in this specification utilize the JWS
skipping to change at page 4, line 5 skipping to change at page 4, line 5
Code", "Authorization Endpoint", "Authorization Grant", Code", "Authorization Endpoint", "Authorization Grant",
"Authorization Server", "Client", "Client Authentication", "Client "Authorization Server", "Client", "Client Authentication", "Client
Identifier", "Client Secret", "Grant Type", "Protected Resource", Identifier", "Client Secret", "Grant Type", "Protected Resource",
"Redirection URI", "Refresh Token", "Resource Owner", "Resource "Redirection URI", "Refresh Token", "Resource Owner", "Resource
Server", "Response Type", and "Token Endpoint" defined by OAuth 2.0 Server", "Response Type", and "Token Endpoint" defined by OAuth 2.0
[RFC6749], the terms "Claim Name", "Claim Value", and "JSON Web Token [RFC6749], the terms "Claim Name", "Claim Value", and "JSON Web Token
(JWT)" defined by JSON Web Token (JWT) [JWT], and the term "Response (JWT)" defined by JSON Web Token (JWT) [JWT], and the term "Response
Mode" defined by OAuth 2.0 Multiple Response Type Encoding Practices Mode" defined by OAuth 2.0 Multiple Response Type Encoding Practices
[OAuth.Responses]. [OAuth.Responses].
This specification also defines the following terms: 2. Authorization Server Metadata
Resource
Entity that is the target of a request in WebFinger.
Host
Server where a WebFinger service is hosted.
2. Authorization Server WebFinger Discovery
Authorization server WebFinger discovery is a means of determining
the location of the authorization server's configuration information.
WebFinger discovery is OPTIONAL; if a client knows the authorization
server's configuration information location through an out-of-band
mechanism, it can skip this step and proceed to Section 4.
WebFinger discovery requires the following information to make a
discovery request:
resource
Identifier for the target resource owner that is the subject of
the discovery request.
host
Server where the WebFinger service is hosted.
rel
URI identifying the type of service whose location is being
requested.
OAuth discovery uses the following "rel" value in WebFinger
[RFC7033]:
+----------------------+--------------------------------------------+
| Rel Type | URI |
+----------------------+--------------------------------------------+
| OAuth 2.0 | http://openid.net/specs/connect/1.0/issuer |
| Configuration | |
| Information Location | |
| URL | |
+----------------------+--------------------------------------------+
To start discovery of OAuth 2.0 configuration information, the
resource owner supplies a URI to the client that can be used to
discover the corresponding authorization server. In some cases, the
client may know this URI without involvement of the resource owner.
This URI might, for instance, be an e-mail address, an account
identifier, a profile URL, or a service or tenant URL.
The host to which the WebFinger request will be made is obtained from
the URI. The client then makes an HTTP "GET" request to the host's
WebFinger [RFC7033] endpoint using the URI as the "resource"
parameter value and the "rel" value
"http://openid.net/specs/connect/1.0/issuer" to obtain the
authorization server's configuration information location.
The configuration information location MUST be returned in the
WebFinger response as the value of the "href" member of a "links"
array element with "rel" member value
"http://openid.net/specs/connect/1.0/issuer". As described in
Section 6, despite the identifier
"http://openid.net/specs/connect/1.0/issuer" appearing to be OpenID-
specific, its usage in this specification is actually referring to a
general OAuth 2.0 feature that is not specific to OpenID Connect.
(Per Section 7 of WebFinger [RFC7033], obtaining the WebFinger
response may first involve following some redirects.)
The returned configuration information location MUST be a URI RFC
3986 [RFC3986] with a scheme component that MUST be "https", a host
component, and optionally, port and path components and no query or
fragment components. Note that the WebFinger response can return a
configuration information location value using a completely different
scheme, host, port, and path from any contained in the input URI, and
no relationship can be assumed between the input URI and the
resulting configuration information location.
An example WebFinger discovery request follows. To find the
authorization server's configuration information location for the
account identified using the e-mail address syntax "joe@example.com"
and corresponding account URI "acct:joe@example.com", the WebFinger
parameters are as follows:
+---------------------+--------------------------------------------+
| WebFinger Parameter | Value |
+---------------------+--------------------------------------------+
| resource | acct:joe@example.com |
| host | example.com |
| rel | http://openid.net/specs/connect/1.0/issuer |
+---------------------+--------------------------------------------+
The client would make the following WebFinger request to discover the
authorization server's configuration information location (with line
wraps within lines for display purposes only):
GET /.well-known/webfinger
?resource=acct%3Ajoe%40example.com
&rel=http%3A%2F%2Fopenid.net%2Fspecs%2Fconnect%2F1.0%2Fissuer
HTTP/1.1
Host: example.com
HTTP/1.1 200 OK
Content-Type: application/jrd+json
{
"subject": "acct:joe@example.com",
"links":
[
{
"rel": "http://openid.net/specs/connect/1.0/issuer",
"href": "https://server.example.com"
}
]
}
The discovered authorization server configuration information
location is "https://server.example.com".
3. Authorization Server Metadata
Authorization servers can have metadata describing their Authorization servers can have metadata describing their
configuration. These authorization server metadata values are used configuration. These authorization server metadata values are used
by this specification: by this specification:
issuer issuer
REQUIRED. URL of the authorization server's configuration REQUIRED. The authorization server's issuer identifier, which is
information location, which uses the "https" scheme and has no a URL that uses the "https" scheme and has no query or fragment
query or fragment components. This is the location where components. This is the location where ".well-known" RFC 5785
".well-known" RFC 5785 [RFC5785] resources containing information [RFC5785] resources containing information about the authorization
about the authorization server are published, and in particular, server are published. Using these well-known resources is
the "/.well-known/openid-configuration" resource defined in described in Section 3. The issuer identifier is used to prevent
Section 4. If WebFinger discovery is supported (see Section 2), authorization server mix-up attacks, as described in "OAuth 2.0
this value MUST be identical to the configuration information Mix-Up Mitigation" [I-D.jones-oauth-mix-up-mitigation].
location value returned by WebFinger.
authorization_endpoint authorization_endpoint
REQUIRED. URL of the authorization server's authorization REQUIRED. URL of the authorization server's authorization
endpoint [RFC6749]. endpoint [RFC6749].
token_endpoint token_endpoint
URL of the authorization server's token endpoint [RFC6749]. This URL of the authorization server's token endpoint [RFC6749]. This
is REQUIRED unless only the implicit grant type is used. is REQUIRED unless only the implicit grant type is used.
jwks_uri jwks_uri
REQUIRED. URL of the authorization server's JWK Set [JWK] REQUIRED. URL of the authorization server's JWK Set [JWK]
document. This contains the signing key(s) the client uses to document. This contains the signing key(s) the client uses to
validate signatures from the authorization server. The JWK Set validate signatures from the authorization server. The JWK Set
MAY also contain the Server's encryption key(s), which are used by MAY also contain the server's encryption key(s), which are used by
RPs to encrypt requests to the Server. When both signing and clients to encrypt requests to the server. When both signing and
encryption keys are made available, a "use" (public key use) encryption keys are made available, a "use" (public key use)
parameter value is REQUIRED for all keys in the referenced JWK Set parameter value is REQUIRED for all keys in the referenced JWK Set
to indicate each key's intended usage. Although some algorithms to indicate each key's intended usage. Although some algorithms
allow the same key to be used for both signatures and encryption, allow the same key to be used for both signatures and encryption,
doing so is NOT RECOMMENDED, as it is less secure. The JWK "x5c" doing so is NOT RECOMMENDED, as it is less secure. The JWK "x5c"
parameter MAY be used to provide X.509 representations of keys parameter MAY be used to provide X.509 representations of keys
provided. When used, the bare key values MUST still be present provided. When used, the bare key values MUST still be present
and MUST match those in the certificate. and MUST match those in the certificate.
registration_endpoint registration_endpoint
skipping to change at page 8, line 45 skipping to change at page 6, line 11
OPTIONAL. Languages and scripts supported for the user interface, OPTIONAL. Languages and scripts supported for the user interface,
represented as a JSON array of BCP47 [RFC5646] language tag represented as a JSON array of BCP47 [RFC5646] language tag
values. values.
op_policy_uri op_policy_uri
OPTIONAL. URL that the authorization server provides to the OPTIONAL. URL that the authorization server provides to the
person registering the client to read about the authorization person registering the client to read about the authorization
server's requirements on how the client can use the data provided server's requirements on how the client can use the data provided
by the authorization server. The registration process SHOULD by the authorization server. The registration process SHOULD
display this URL to the person registering the client if it is display this URL to the person registering the client if it is
given. As described in Section 6, despite the identifier given. As described in Section 5, despite the identifier
"op_policy_uri", appearing to be OpenID-specific, its usage in "op_policy_uri", appearing to be OpenID-specific, its usage in
this specification is actually referring to a general OAuth 2.0 this specification is actually referring to a general OAuth 2.0
feature that is not specific to OpenID Connect. feature that is not specific to OpenID Connect.
op_tos_uri op_tos_uri
OPTIONAL. URL that the authorization server provides to the OPTIONAL. URL that the authorization server provides to the
person registering the client to read about authorization server's person registering the client to read about authorization server's
terms of service. The registration process SHOULD display this terms of service. The registration process SHOULD display this
URL to the person registering the client if it is given. As URL to the person registering the client if it is given. As
described in Section 6, despite the identifier "op_tos_uri", described in Section 5, despite the identifier "op_tos_uri",
appearing to be OpenID-specific, its usage in this specification appearing to be OpenID-specific, its usage in this specification
is actually referring to a general OAuth 2.0 feature that is not is actually referring to a general OAuth 2.0 feature that is not
specific to OpenID Connect. specific to OpenID Connect.
revocation_endpoint revocation_endpoint
OPTIONAL. URL of the authorization server's OAuth 2.0 revocation OPTIONAL. URL of the authorization server's OAuth 2.0 revocation
endpoint [RFC7009]. endpoint [RFC7009].
revocation_endpoint_auth_methods_supported revocation_endpoint_auth_methods_supported
OPTIONAL. JSON array containing a list of client authentication OPTIONAL. JSON array containing a list of client authentication
skipping to change at page 9, line 45 skipping to change at page 7, line 7
OPTIONAL. URL of the authorization server's OAuth 2.0 OPTIONAL. URL of the authorization server's OAuth 2.0
introspection endpoint [RFC7662]. introspection endpoint [RFC7662].
introspection_endpoint_auth_methods_supported introspection_endpoint_auth_methods_supported
OPTIONAL. JSON array containing a list of client authentication OPTIONAL. JSON array containing a list of client authentication
methods supported by this introspection endpoint. The valid methods supported by this introspection endpoint. The valid
client authentication method values are those registered in the client authentication method values are those registered in the
IANA "OAuth Token Endpoint Authentication Methods" registry IANA "OAuth Token Endpoint Authentication Methods" registry
[IANA.OAuth.Parameters] or those registered in the IANA "OAuth [IANA.OAuth.Parameters] or those registered in the IANA "OAuth
Access Token Types" registry [IANA.OAuth.Parameters]. (These Access Token Types" registry [IANA.OAuth.Parameters]. (These
values are and will remain distinct, due to Section 8.2.) values are and will remain distinct, due to Section 7.2.)
introspection_endpoint_auth_signing_alg_values_supported introspection_endpoint_auth_signing_alg_values_supported
OPTIONAL. JSON array containing a list of the JWS signing OPTIONAL. JSON array containing a list of the JWS signing
algorithms ("alg" values) supported by the introspection endpoint algorithms ("alg" values) supported by the introspection endpoint
for the signature on the JWT [JWT] used to authenticate the client for the signature on the JWT [JWT] used to authenticate the client
at the introspection endpoint for the "private_key_jwt" and at the introspection endpoint for the "private_key_jwt" and
"client_secret_jwt" authentication methods. The value "none" MUST "client_secret_jwt" authentication methods. The value "none" MUST
NOT be used. NOT be used.
code_challenge_methods_supported code_challenge_methods_supported
skipping to change at page 10, line 18 skipping to change at page 7, line 29
challenge methods supported by this authorization server. Code challenge methods supported by this authorization server. Code
challenge method values are used in the "code_challenge_method" challenge method values are used in the "code_challenge_method"
parameter defined in Section 4.3 of [RFC7636]. The valid code parameter defined in Section 4.3 of [RFC7636]. The valid code
challenge method values are those registered in the IANA "PKCE challenge method values are those registered in the IANA "PKCE
Code Challenge Methods" registry [IANA.OAuth.Parameters]. Code Challenge Methods" registry [IANA.OAuth.Parameters].
Additional authorization server metadata parameters MAY also be used. Additional authorization server metadata parameters MAY also be used.
Some are defined by other specifications, such as OpenID Connect Some are defined by other specifications, such as OpenID Connect
Discovery 1.0 [OpenID.Discovery]. Discovery 1.0 [OpenID.Discovery].
4. Obtaining Authorization Server Configuration Information 3. Obtaining Authorization Server Discovery Metadata
Using the configuration information location discovered as described
in Section 2 or by other means, the authorization server's
configuration information can be retrieved.
Authorization servers supporting discovery MUST make a JSON document Authorization servers supporting discovery MUST make a JSON document
available at the path formed by concatenating the string containing discovery metadata as specified in Section 2 available at
"/.well-known/openid-configuration" to the configuration information a path formed by concatenating a well-known URI string such as
location. The syntax and semantics of ".well-known" are defined in "/.well-known/openid-configuration" to the authorization server's
RFC 5785 [RFC5785] and apply to the configuration information issuer identifier. The syntax and semantics of ".well-known" are
location value when it contains no path component. defined in RFC 5785 [RFC5785]. The well-known URI path suffix used
"openid-configuration" MUST point to a JSON document compliant with MUST be registered in the IANA "Well-Known URIs" registry
this specification and MUST be returned using the "application/json" [IANA.well-known].
content type. As described in Section 6, despite the identifier
Different applications utilizing OAuth authorization servers in
application-specific ways may define and register different well-
known URI path suffixes used to publish authorization server metadata
as used by those applications. For instance, if the Example
application uses an OAuth authorization server in an Example-specific
way, and there are Example-specific metadata values that it needs to
publish, then it might register and use the "example" URI path suffix
and publish the metadata document at the path formed by concatenating
"/.well-known/example-configuration" to the authorization server's
issuer identifier.
By default, for historical reasons, unless an application-specific
well-known URI path suffix is registered and used for an application,
the client for that application SHOULD use the well-known URI path
suffix "openid-configuration" and publish the metadata document at
the path formed by concatenating "/.well-known/openid-configuration"
to the authorization server's issuer identifier. As described in
Section 5, despite the identifier
"/.well-known/openid-configuration", appearing to be OpenID-specific, "/.well-known/openid-configuration", appearing to be OpenID-specific,
its usage in this specification is actually referring to a general its usage in this specification is actually referring to a general
OAuth 2.0 feature that is not specific to OpenID Connect. OAuth 2.0 feature that is not specific to OpenID Connect.
4.1. Authorization Server Configuration Information Request 3.1. Authorization Server Discovery Metadata Request
An authorization server configuration information document MUST be An authorization server discovery metadata document MUST be queried
queried using an HTTP "GET" request at the previously specified path. using an HTTP "GET" request at the previously specified path.
The client would make the following request to the configuration The client would make the following request when the issuer
information location "https://example.com" to obtain its identifier is "https://example.com" and the well-known URI path
configuration information, since the configuration information suffix is "openid-configuration" to obtain the discovery metadata,
location contains no path component: since the issuer identifier contains no path component:
GET /.well-known/openid-configuration HTTP/1.1 GET /.well-known/openid-configuration HTTP/1.1
Host: example.com Host: example.com
If the configuration information location value contains a path If the issuer identifier value contains a path component, any
component, any terminating "/" MUST be removed before appending terminating "/" MUST be removed before appending "/.well-known/" and
"/.well-known/openid-configuration". The client would make the the well-known URI path suffix. The client would make the following
following request to the configuration information location request when the issuer identifier is "https://example.com/issuer1"
"https://example.com/issuer1" to obtain its configuration and the well-known URI path suffix is "openid-configuration" to
information, since the configuration information location contains a obtain the discovery metadata, since the issuer identifier contains a
path component: path component:
GET /issuer1/.well-known/openid-configuration HTTP/1.1 GET /issuer1/.well-known/openid-configuration HTTP/1.1
Host: example.com Host: example.com
Using path components enables supporting multiple issuers per host. Using path components enables supporting multiple issuers per host.
This is required in some multi-tenant hosting configurations. This This is required in some multi-tenant hosting configurations. This
use of ".well-known" is for supporting multiple issuers per host; use of ".well-known" is for supporting multiple issuers per host;
unlike its use in RFC 5785 [RFC5785], it does not provide general unlike its use in RFC 5785 [RFC5785], it does not provide general
information about the host. information about the host.
4.2. Authorization Server Configuration Information Response 3.2. Authorization Server Discovery Metadata Response
The response is a set of claims about the authorization server's The response is a set of claims about the authorization server's
configuration, including all necessary endpoints and public key configuration, including all necessary endpoints and public key
location information. A successful response MUST use the 200 OK HTTP location information. A successful response MUST use the 200 OK HTTP
status code and return a JSON object using the "application/json" status code and return a JSON object using the "application/json"
content type that contains a set of claims as its members that are a content type that contains a set of claims as its members that are a
subset of the metadata values defined in Section 3. Other claims MAY subset of the metadata values defined in Section 2. Other claims MAY
also be returned. also be returned.
Claims that return multiple values are represented as JSON arrays. Claims that return multiple values are represented as JSON arrays.
Claims with zero elements MUST be omitted from the response. Claims with zero elements MUST be omitted from the response.
An error response uses the applicable HTTP status code value. An error response uses the applicable HTTP status code value.
The following is a non-normative example response: The following is a non-normative example response:
HTTP/1.1 200 OK HTTP/1.1 200 OK
skipping to change at page 12, line 38 skipping to change at page 9, line 47
["openid", "profile", "email", "address", ["openid", "profile", "email", "address",
"phone", "offline_access"], "phone", "offline_access"],
"response_types_supported": "response_types_supported":
["code", "code token"], ["code", "code token"],
"service_documentation": "service_documentation":
"http://server.example.com/connect/service_documentation.html", "http://server.example.com/connect/service_documentation.html",
"ui_locales_supported": "ui_locales_supported":
["en-US", "en-GB", "en-CA", "fr-FR", "fr-CA"] ["en-US", "en-GB", "en-CA", "fr-FR", "fr-CA"]
} }
4.3. Authorization Server Configuration Information Validation 3.3. Authorization Server Discovery Metadata Validation
If any of the validation procedures defined in this specification
fail, any operations requiring the information that failed to
correctly validate MUST be aborted and the information that failed to
validate MUST NOT be used.
The "issuer" value returned MUST be identical to the configuration The "issuer" value returned MUST be identical to the authorization
information location URL that was directly used to retrieve the server's issuer identifier value that was concatenated with the well-
configuration information. known URI path suffix to create the URL used to retrieve the
discovery metadata. If these values are not identical, the data
contained in the response MUST NOT be used.
5. String Operations 4. String Operations
Processing some OAuth 2.0 messages requires comparing values in the Processing some OAuth 2.0 messages requires comparing values in the
messages to known values. For example, the member names in the messages to known values. For example, the member names in the
configuration information response might be compared to specific discovery metadata response might be compared to specific member
member names such as "issuer". Comparing Unicode [UNICODE] strings, names such as "issuer". Comparing Unicode [UNICODE] strings,
however, has significant security implications. however, has significant security implications.
Therefore, comparisons between JSON strings and other Unicode strings Therefore, comparisons between JSON strings and other Unicode strings
MUST be performed as specified below: MUST be performed as specified below:
1. Remove any JSON applied escaping to produce an array of Unicode 1. Remove any JSON applied escaping to produce an array of Unicode
code points. code points.
2. Unicode Normalization [USA15] MUST NOT be applied at any point to 2. Unicode Normalization [USA15] MUST NOT be applied at any point to
either the JSON string or to the string it is to be compared either the JSON string or to the string it is to be compared
against. against.
3. Comparisons between the two strings MUST be performed as a 3. Comparisons between the two strings MUST be performed as a
Unicode code point to code point equality comparison. Unicode code point to code point equality comparison.
6. Compatibility Notes 5. Compatibility Notes
The identifiers "/.well-known/openid-configuration", The identifiers "/.well-known/openid-configuration",
"http://openid.net/specs/connect/1.0/issuer", "op_policy_uri", and "http://openid.net/specs/connect/1.0/issuer", "op_policy_uri", and
"op_tos_uri" contain strings referring to the OpenID Connect "op_tos_uri" contain strings referring to the OpenID Connect
[OpenID.Core] family of specifications that were originally defined [OpenID.Core] family of specifications that were originally defined
by "OpenID Connect Discovery 1.0" [OpenID.Discovery]. Despite the by "OpenID Connect Discovery 1.0" [OpenID.Discovery]. Despite the
reuse of these identifiers that appear to be OpenID-specific, their reuse of these identifiers that appear to be OpenID-specific, their
usage in this specification is actually referring to general OAuth usage in this specification is actually referring to general OAuth
2.0 features that are not specific to OpenID Connect. 2.0 features that are not specific to OpenID Connect.
7. Security Considerations 6. Security Considerations
7.1. TLS Requirements 6.1. TLS Requirements
Implementations MUST support TLS. Which version(s) ought to be Implementations MUST support TLS. Which version(s) ought to be
implemented will vary over time, and depend on the widespread implemented will vary over time, and depend on the widespread
deployment and known security vulnerabilities at the time of deployment and known security vulnerabilities at the time of
implementation. The authorization server MUST support TLS version implementation. The authorization server MUST support TLS version
1.2 [RFC5246] and MAY support additional transport-layer security 1.2 [RFC5246] and MAY support additional transport-layer security
mechanisms meeting its security requirements. When using TLS, the mechanisms meeting its security requirements. When using TLS, the
client MUST perform a TLS/SSL server certificate check, per RFC 6125 client MUST perform a TLS/SSL server certificate check, per RFC 6125
[RFC6125]. Implementation security considerations can be found in [RFC6125]. Implementation security considerations can be found in
Recommendations for Secure Use of TLS and DTLS [BCP195]. Recommendations for Secure Use of TLS and DTLS [BCP195].
To protect against information disclosure and tampering, To protect against information disclosure and tampering,
confidentiality protection MUST be applied using TLS with a confidentiality protection MUST be applied using TLS with a
ciphersuite that provides confidentiality and integrity protection. ciphersuite that provides confidentiality and integrity protection.
7.2. Impersonation Attacks 6.2. Impersonation Attacks
TLS certificate checking MUST be performed by the client, as TLS certificate checking MUST be performed by the client, as
described in Section 7.1, when making an authorization server described in Section 6.1, when making an authorization server
configuration information request. Checking that the server discovery metadata request. Checking that the server certificate is
certificate is valid for the configuration information location URL valid for the issuer identifier URL prevents man-in-middle and DNS-
prevents man-in-middle and DNS-based attacks. These attacks could based attacks. These attacks could cause a client to be tricked into
cause a client to be tricked into using an attacker's keys and using an attacker's keys and endpoints, which would enable
endpoints, which would enable impersonation of the legitimate impersonation of the legitimate authorization server. If an attacker
authorization server. If an attacker can accomplish this, they can can accomplish this, they can access the resources that the affected
access the resources that the affected client has access to using the client has access to using the authorization server that they are
authorization server that they are impersonating. impersonating.
An attacker may also attempt to impersonate an authorization server An attacker may also attempt to impersonate an authorization server
by publishing a discovery document that contains an "issuer" claim by publishing a discovery document that contains an "issuer" claim
using the configuration information location URL of the authorization using the issuer identifier URL of the authorization server being
server being impersonated, but with its own endpoints and signing impersonated, but with its own endpoints and signing keys. This
keys. This would enable it to impersonate that authorization server, would enable it to impersonate that authorization server, if accepted
if accepted by the client. To prevent this, RPs MUST ensure that the by the client. To prevent this, the client MUST ensure that the
configuration information location URL they are using for the issuer identifier URL it is using as the prefix for the discovery
configuration information request exactly matches the value of the metadata request exactly matches the value of the "issuer" metadata
"issuer" metadata value in the authorization server configuration value in the authorization server discovery metadata document
information document received by the client. received by the client.
8. IANA Considerations 7. IANA Considerations
The following registration procedure is used for the registry The following registration procedure is used for the registry
established by this specification. established by this specification.
Values are registered on a Specification Required [RFC5226] basis Values are registered on a Specification Required [RFC5226] basis
after a two-week review period on the oauth-ext-review@ietf.org after a two-week review period on the oauth-ext-review@ietf.org
mailing list, on the advice of one or more Designated Experts. mailing list, on the advice of one or more Designated Experts.
However, to allow for the allocation of values prior to publication, However, to allow for the allocation of values prior to publication,
the Designated Experts may approve registration once they are the Designated Experts may approve registration once they are
satisfied that such a specification will be published. satisfied that such a specification will be published.
skipping to change at page 15, line 23 skipping to change at page 12, line 31
list. list.
It is suggested that multiple Designated Experts be appointed who are It is suggested that multiple Designated Experts be appointed who are
able to represent the perspectives of different applications using able to represent the perspectives of different applications using
this specification, in order to enable broadly-informed review of this specification, in order to enable broadly-informed review of
registration decisions. In cases where a registration decision could registration decisions. In cases where a registration decision could
be perceived as creating a conflict of interest for a particular be perceived as creating a conflict of interest for a particular
Expert, that Expert should defer to the judgment of the other Expert, that Expert should defer to the judgment of the other
Experts. Experts.
8.1. OAuth Discovery Metadata Registry 7.1. OAuth Discovery Metadata Registry
This specification establishes the IANA "OAuth Discovery Metadata" This specification establishes the IANA "OAuth Discovery Metadata"
registry for OAuth 2.0 authorization server metadata names. The registry for OAuth 2.0 authorization server metadata names. The
registry records the authorization server metadata member and a registry records the authorization server metadata member and a
reference to the specification that defines it. reference to the specification that defines it.
8.1.1. Registration Template 7.1.1. Registration Template
Discovery Metadata Name: Discovery Metadata Name:
The name requested (e.g., "issuer"). This name is case-sensitive. The name requested (e.g., "issuer"). This name is case-sensitive.
Names may not match other registered names in a case-insensitive Names may not match other registered names in a case-insensitive
manner unless the Designated Experts state that there is a manner unless the Designated Experts state that there is a
compelling reason to allow an exception. compelling reason to allow an exception.
Discovery Metadata Description: Discovery Metadata Description:
Brief description of the discovery metadata (e.g., "Issuer URL"). Brief description of the discovery metadata (e.g., "Issuer URL").
skipping to change at page 16, line 5 skipping to change at page 13, line 11
For Standards Track RFCs, list the "IESG". For others, give the For Standards Track RFCs, list the "IESG". For others, give the
name of the responsible party. Other details (e.g., postal name of the responsible party. Other details (e.g., postal
address, email address, home page URI) may also be included. address, email address, home page URI) may also be included.
Specification Document(s): Specification Document(s):
Reference to the document or documents that specify the parameter, Reference to the document or documents that specify the parameter,
preferably including URIs that can be used to retrieve copies of preferably including URIs that can be used to retrieve copies of
the documents. An indication of the relevant sections may also be the documents. An indication of the relevant sections may also be
included but is not required. included but is not required.
8.1.2. Initial Registry Contents 7.1.2. Initial Registry Contents
o Discovery Metadata Name: "issuer" o Discovery Metadata Name: "issuer"
o Discovery Metadata Description: URL of the authorization server's o Discovery Metadata Description: Authorization server's issuer
configuration information location identifier URL
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 3 of [[ this specification ]] o Specification Document(s): Section 2 of [[ this specification ]]
o Discovery Metadata Name: "authorization_endpoint" o Discovery Metadata Name: "authorization_endpoint"
o Discovery Metadata Description: URL of the authorization server's o Discovery Metadata Description: URL of the authorization server's
authorization endpoint authorization endpoint
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 3 of [[ this specification ]] o Specification Document(s): Section 2 of [[ this specification ]]
o Discovery Metadata Name: "token_endpoint" o Discovery Metadata Name: "token_endpoint"
o Discovery Metadata Description: URL of the authorization server's o Discovery Metadata Description: URL of the authorization server's
token endpoint token endpoint
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 3 of [[ this specification ]] o Specification Document(s): Section 2 of [[ this specification ]]
o Discovery Metadata Name: "jwks_uri" o Discovery Metadata Name: "jwks_uri"
o Discovery Metadata Description: URL of the authorization server's o Discovery Metadata Description: URL of the authorization server's
JWK Set document JWK Set document
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 3 of [[ this specification ]] o Specification Document(s): Section 2 of [[ this specification ]]
o Discovery Metadata Name: "registration_endpoint" o Discovery Metadata Name: "registration_endpoint"
o Discovery Metadata Description: URL of the authorization server's o Discovery Metadata Description: URL of the authorization server's
OAuth 2.0 Dynamic Client Registration Endpoint OAuth 2.0 Dynamic Client Registration Endpoint
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 3 of [[ this specification ]] o Specification Document(s): Section 2 of [[ this specification ]]
o Discovery Metadata Name: "scopes_supported" o Discovery Metadata Name: "scopes_supported"
o Discovery Metadata Description: JSON array containing a list of o Discovery Metadata Description: JSON array containing a list of
the OAuth 2.0 "scope" values that this authorization server the OAuth 2.0 "scope" values that this authorization server
supports supports
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 3 of [[ this specification ]] o Specification Document(s): Section 2 of [[ this specification ]]
o Discovery Metadata Name: "response_types_supported" o Discovery Metadata Name: "response_types_supported"
o Discovery Metadata Description: JSON array containing a list of o Discovery Metadata Description: JSON array containing a list of
the OAuth 2.0 "response_type" values that this authorization the OAuth 2.0 "response_type" values that this authorization
server supports server supports
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 3 of [[ this specification ]] o Specification Document(s): Section 2 of [[ this specification ]]
o Discovery Metadata Name: "response_modes_supported" o Discovery Metadata Name: "response_modes_supported"
o Discovery Metadata Description: JSON array containing a list of o Discovery Metadata Description: JSON array containing a list of
the OAuth 2.0 "response_mode" values that this authorization the OAuth 2.0 "response_mode" values that this authorization
server supports server supports
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 3 of [[ this specification ]] o Specification Document(s): Section 2 of [[ this specification ]]
o Discovery Metadata Name: "grant_types_supported" o Discovery Metadata Name: "grant_types_supported"
o Discovery Metadata Description: JSON array containing a list of o Discovery Metadata Description: JSON array containing a list of
the OAuth 2.0 grant type values that this authorization server the OAuth 2.0 grant type values that this authorization server
supports supports
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 3 of [[ this specification ]] o Specification Document(s): Section 2 of [[ this specification ]]
o Discovery Metadata Name: "token_endpoint_auth_methods_supported" o Discovery Metadata Name: "token_endpoint_auth_methods_supported"
o Discovery Metadata Description: JSON array containing a list of o Discovery Metadata Description: JSON array containing a list of
client authentication methods supported by this token endpoint client authentication methods supported by this token endpoint
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 3 of [[ this specification ]] o Specification Document(s): Section 2 of [[ this specification ]]
o Discovery Metadata Name: o Discovery Metadata Name:
"token_endpoint_auth_signing_alg_values_supported" "token_endpoint_auth_signing_alg_values_supported"
o Discovery Metadata Description: JSON array containing a list of o Discovery Metadata Description: JSON array containing a list of
the JWS signing algorithms supported by the token endpoint for the the JWS signing algorithms supported by the token endpoint for the
signature on the JWT used to authenticate the client at the token signature on the JWT used to authenticate the client at the token
endpoint endpoint
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 3 of [[ this specification ]] o Specification Document(s): Section 2 of [[ this specification ]]
o Discovery Metadata Name: "service_documentation" o Discovery Metadata Name: "service_documentation"
o Discovery Metadata Description: URL of a page containing human- o Discovery Metadata Description: URL of a page containing human-
readable information that developers might want or need to know readable information that developers might want or need to know
when using the authorization server when using the authorization server
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 3 of [[ this specification ]] o Specification Document(s): Section 2 of [[ this specification ]]
o Discovery Metadata Name: "ui_locales_supported" o Discovery Metadata Name: "ui_locales_supported"
o Discovery Metadata Description: Languages and scripts supported o Discovery Metadata Description: Languages and scripts supported
for the user interface, represented as a JSON array of BCP47 for the user interface, represented as a JSON array of BCP47
language tag values language tag values
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 3 of [[ this specification ]] o Specification Document(s): Section 2 of [[ this specification ]]
o Discovery Metadata Name: "op_policy_uri" o Discovery Metadata Name: "op_policy_uri"
o Discovery Metadata Description: URL that the authorization server o Discovery Metadata Description: URL that the authorization server
provides to the person registering the client to read about the provides to the person registering the client to read about the
authorization server's requirements on how the client can use the authorization server's requirements on how the client can use the
data provided by the authorization server data provided by the authorization server
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 3 of [[ this specification ]] o Specification Document(s): Section 2 of [[ this specification ]]
o Discovery Metadata Name: "op_tos_uri" o Discovery Metadata Name: "op_tos_uri"
o Discovery Metadata Description: URL that the authorization server o Discovery Metadata Description: URL that the authorization server
provides to the person registering the client to read about provides to the person registering the client to read about
authorization server's terms of service authorization server's terms of service
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 3 of [[ this specification ]] o Specification Document(s): Section 2 of [[ this specification ]]
o Discovery Metadata Name: "revocation_endpoint" o Discovery Metadata Name: "revocation_endpoint"
o Discovery Metadata Description: URL of the authorization server's o Discovery Metadata Description: URL of the authorization server's
OAuth 2.0 revocation endpoint OAuth 2.0 revocation endpoint
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 3 of [[ this specification ]] o Specification Document(s): Section 2 of [[ this specification ]]
o Discovery Metadata Name: o Discovery Metadata Name:
"revocation_endpoint_auth_methods_supported" "revocation_endpoint_auth_methods_supported"
o Discovery Metadata Description: JSON array containing a list of o Discovery Metadata Description: JSON array containing a list of
client authentication methods supported by this revocation client authentication methods supported by this revocation
endpoint endpoint
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 3 of [[ this specification ]] o Specification Document(s): Section 2 of [[ this specification ]]
o Discovery Metadata Name: o Discovery Metadata Name:
"revocation_endpoint_auth_signing_alg_values_supported" "revocation_endpoint_auth_signing_alg_values_supported"
o Discovery Metadata Description: JSON array containing a list of o Discovery Metadata Description: JSON array containing a list of
the JWS signing algorithms supported by the revocation endpoint the JWS signing algorithms supported by the revocation endpoint
for the signature on the JWT used to authenticate the client at for the signature on the JWT used to authenticate the client at
the revocation endpoint the revocation endpoint
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 3 of [[ this specification ]] o Specification Document(s): Section 2 of [[ this specification ]]
o Discovery Metadata Name: "introspection_endpoint" o Discovery Metadata Name: "introspection_endpoint"
o Discovery Metadata Description: URL of the authorization server's o Discovery Metadata Description: URL of the authorization server's
OAuth 2.0 introspection endpoint OAuth 2.0 introspection endpoint
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 3 of [[ this specification ]] o Specification Document(s): Section 2 of [[ this specification ]]
o Discovery Metadata Name: o Discovery Metadata Name:
"introspection_endpoint_auth_methods_supported" "introspection_endpoint_auth_methods_supported"
o Discovery Metadata Description: JSON array containing a list of o Discovery Metadata Description: JSON array containing a list of
client authentication methods supported by this introspection client authentication methods supported by this introspection
endpoint endpoint
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 3 of [[ this specification ]] o Specification Document(s): Section 2 of [[ this specification ]]
o Discovery Metadata Name: o Discovery Metadata Name:
"introspection_endpoint_auth_signing_alg_values_supported" "introspection_endpoint_auth_signing_alg_values_supported"
o Discovery Metadata Description: JSON array containing a list of o Discovery Metadata Description: JSON array containing a list of
the JWS signing algorithms supported by the introspection endpoint the JWS signing algorithms supported by the introspection endpoint
for the signature on the JWT used to authenticate the client at for the signature on the JWT used to authenticate the client at
the introspection endpoint the introspection endpoint
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 3 of [[ this specification ]] o Specification Document(s): Section 2 of [[ this specification ]]
o Discovery Metadata Name: "code_challenge_methods_supported" o Discovery Metadata Name: "code_challenge_methods_supported"
o Discovery Metadata Description: PKCE code challenge methods o Discovery Metadata Description: PKCE code challenge methods
supported by this authorization server supported by this authorization server
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 3 of [[ this specification ]] o Specification Document(s): Section 2 of [[ this specification ]]
8.2. Updated Registration Instructions 7.2. Updated Registration Instructions
This specification adds to the instructions for the Designated This specification adds to the instructions for the Designated
Experts of the following IANA registries, both of which are in the Experts of the following IANA registries, both of which are in the
"OAuth Parameters" registry [IANA.OAuth.Parameters]: "OAuth Parameters" registry [IANA.OAuth.Parameters]:
o OAuth Access Token Types o OAuth Access Token Types
o OAuth Token Endpoint Authentication Methods o OAuth Token Endpoint Authentication Methods
IANA has added a link to this specification in the Reference sections IANA has added a link to this specification in the Reference sections
of these registries. [[ RFC Editor: The above sentence is written in of these registries. [[ RFC Editor: The above sentence is written in
the past tense as it would appear in the final specification, even the past tense as it would appear in the final specification, even
skipping to change at page 19, line 42 skipping to change at page 16, line 50
after the links are in place. ]] after the links are in place. ]]
For these registries, the designated experts must reject registration For these registries, the designated experts must reject registration
requests in one registry for values already occurring in the other requests in one registry for values already occurring in the other
registry. This is necessary because the registry. This is necessary because the
"introspection_endpoint_auth_methods_supported" parameter allows for "introspection_endpoint_auth_methods_supported" parameter allows for
the use of values from either registry. That way, because the values the use of values from either registry. That way, because the values
in the two registries will continue to be mutually exclusive, no in the two registries will continue to be mutually exclusive, no
ambiguities will arise. ambiguities will arise.
9. References 8. References
8.1. Normative References
9.1. Normative References
[BCP195] Sheffer, Y., Holz, R., and P. Saint-Andre, [BCP195] Sheffer, Y., Holz, R., and P. Saint-Andre,
"Recommendations for Secure Use of Transport Layer "Recommendations for Secure Use of Transport Layer
Security (TLS) and Datagram Transport Layer Security Security (TLS) and Datagram Transport Layer Security
(DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, (DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525,
May 2015, <http://www.rfc-editor.org/info/bcp195>. May 2015, <http://www.rfc-editor.org/info/bcp195>.
[IANA.OAuth.Parameters] [IANA.OAuth.Parameters]
IANA, "OAuth Parameters", IANA, "OAuth Parameters",
<http://www.iana.org/assignments/oauth-parameters>. <http://www.iana.org/assignments/oauth-parameters>.
skipping to change at page 22, line 23 skipping to change at page 19, line 31
RFC 7662, DOI 10.17487/RFC7662, October 2015, RFC 7662, DOI 10.17487/RFC7662, October 2015,
<http://www.rfc-editor.org/info/rfc7662>. <http://www.rfc-editor.org/info/rfc7662>.
[UNICODE] The Unicode Consortium, "The Unicode Standard", [UNICODE] The Unicode Consortium, "The Unicode Standard",
<http://www.unicode.org/versions/latest/>. <http://www.unicode.org/versions/latest/>.
[USA15] Davis, M. and K. Whistler, "Unicode Normalization Forms", [USA15] Davis, M. and K. Whistler, "Unicode Normalization Forms",
Unicode Standard Annex 15, June 2015, Unicode Standard Annex 15, June 2015,
<http://www.unicode.org/reports/tr15/>. <http://www.unicode.org/reports/tr15/>.
9.2. Informative References 8.2. Informative References
[I-D.jones-oauth-mix-up-mitigation]
Jones, M. and J. Bradley, "OAuth 2.0 Mix-Up Mitigation",
draft-jones-oauth-mix-up-mitigation-01 (work in progress),
January 2016.
[IANA.well-known]
IANA, "Well-Known URIs",
<http://www.iana.org/assignments/well-known-uris>.
[OpenID.Core] [OpenID.Core]
Sakimura, N., Bradley, J., Jones, M., de Medeiros, B., and Sakimura, N., Bradley, J., Jones, M., de Medeiros, B., and
C. Mortimore, "OpenID Connect Core 1.0", November 2014, C. Mortimore, "OpenID Connect Core 1.0", November 2014,
<http://openid.net/specs/openid-connect-core-1_0.html>. <http://openid.net/specs/openid-connect-core-1_0.html>.
[OpenID.Discovery] [OpenID.Discovery]
Sakimura, N., Bradley, J., Jones, M., and E. Jay, "OpenID Sakimura, N., Bradley, J., Jones, M., and E. Jay, "OpenID
Connect Discovery 1.0", November 2014, <http://openid.net/ Connect Discovery 1.0", November 2014, <http://openid.net/
specs/openid-connect-discovery-1_0.html>. specs/openid-connect-discovery-1_0.html>.
skipping to change at page 23, line 4 skipping to change at page 20, line 19
Appendix A. Acknowledgements Appendix A. Acknowledgements
This specification is based on the OpenID Connect Discovery 1.0 This specification is based on the OpenID Connect Discovery 1.0
specification, which was produced by the OpenID Connect working group specification, which was produced by the OpenID Connect working group
of the OpenID Foundation. of the OpenID Foundation.
Appendix B. Document History Appendix B. Document History
[[ to be removed by the RFC Editor before publication as an RFC ]] [[ to be removed by the RFC Editor before publication as an RFC ]]
-01
o Removed WebFinger discovery.
o Clarified the relationship between the issuer identifier URL and
the well-known URI path relative to it at which the discovery
metadata document is located.
-00 -00
o Created the initial working group version based on o Created the initial working group version based on
draft-jones-oauth-discovery-01, with no normative changes. draft-jones-oauth-discovery-01, with no normative changes.
Authors' Addresses Authors' Addresses
Michael B. Jones Michael B. Jones
Microsoft Microsoft
 End of changes. 66 change blocks. 
272 lines changed or deleted 180 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/