| Internet-Draft | OpenID Connect for RDAP | July 2023 |
| Hollenbeck | Expires 1 February 2024 | [Page] |
The Registration Data Access Protocol (RDAP) provides "RESTful" web services to retrieve registration metadata from domain name and regional internet registries. RDAP allows a server to make access control decisions based on client identity, and as such it includes support for client identification features provided by the Hypertext Transfer Protocol (HTTP). Identification methods that require clients to obtain and manage credentials from every RDAP server operator present management challenges for both clients and servers, whereas a federated authentication system would make it easier to operate and use RDAP without the need to maintain server-specific client credentials. This document describes a federated authentication system for RDAP based on OpenID Connect.¶
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 1 February 2024.¶
Copyright (c) 2023 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 Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
The Registration Data Access Protocol (RDAP) provides "RESTful" web services to retrieve registration metadata from domain name and regional internet registries. RDAP allows a server to make access control decisions based on client identity, and as such it includes support for client identification features provided by the Hypertext Transfer Protocol (HTTP) [RFC9110].¶
RDAP is specified in multiple documents, including "HTTP Usage in the Registration Data Access Protocol (RDAP)" [RFC7480], "Security Services for the Registration Data Access Protocol (RDAP)" [RFC7481], "Registration Data Access Protocol Query Format" [RFC9082], and "JSON Responses for the Registration Data Access Protocol (RDAP)" [RFC9083]. RFC 7481 describes client identification and authentication services that can be used with RDAP, but it does not specify how any of these services can (or should) be used with RDAP.¶
The traditional "user name and password" authentication method does not scale well in the RDAP ecosystem. Assuming that all domain name and address registries will eventually provide RDAP service, it is impractical and inefficient for users to secure login credentials from the hundreds of different server operators. Authentication methods based on user names and passwords do not provide information that describes the user in sufficient detail (while protecting the personal privacy of the user) for server operators to make fine-grained access control decisions based on the user's identity. The authentication system used for RDAP needs to address all of these needs.¶
A basic level of RDAP service can be provided to users who possess an identifier issued by a recognized provider who can authenticate and validate the user. The identifiers issued by social media services, for example, can be used. Users who require higher levels of service (and who are willing to share more information about themselves to gain access to that service) can secure identifiers from specialized providers who are or will be able to provide more detailed information about the user. Server operators can then make access control decisions based on the identification information provided by the user.¶
A federated authentication system in which an RDAP server outsources identification and authentication services to a trusted OpenID Provider would make it easier to operate and use RDAP by re-using existing identifiers to provide a basic level of access. It can also provide the ability to collect additional user identification information, and that information can be shared with the RDAP server operator with the consent of the user in order to help the server operator make access control decisions. This type of system allows an RDAP server to make access control decisions based on the nature of a query and the identity, authentication, and authorization information that is received from the OpenID Provider. This document describes a federated authentication system for RDAP based on OpenID Connect [OIDC] that meets these needs.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
Unless otherwise specified, all of the HTTP requests described in this document that are sent from an RDAP client to an RDAP server use the HTTP GET method as specified in [RFC9110].¶
RDAP itself does not include native security services. Instead, RDAP relies on features that are available in other protocol layers to provide needed security services including access control, authentication, authorization, availability, data confidentiality, data integrity, and identification. A description of each of these security services can be found in "Internet Security Glossary, Version 2" [RFC4949]. This document focuses on a federated authentication system for RDAP that provides services for authentication, authorization, and identification, allowing a server operator to make access control decisions. Section 3 of RFC 7481 [RFC7481] describes general considerations for RDAP access control, authentication, and authorization.¶
The traditional client-server authentication model requires clients to maintain distinct credentials for every RDAP server. This situation can become unwieldy as the number of RDAP servers increases. Federated authentication mechanisms allow clients to use one credential to access multiple RDAP servers and reduce client credential management complexity.¶
OpenID Connect 1.0 [OIDCC] is a decentralized, single sign-on (SSO) federated authentication system that allows users to access multiple web resources with one identifier instead of having to create multiple server-specific identifiers. Users acquire identifiers from OpenID Providers, or OPs. Relying Parties, or RPs, are applications (such as RDAP) that outsource their user authentication function to an OP. OpenID Connect is built on top of the authorization framework provided by the OAuth 2.0 [RFC6749] protocol.¶
The OAuth authorization framework describes a method for users to access protected web resources without having to hand out their credentials. Instead, clients are issued Access Tokens by OpenID Providers with the permission of the resource owners. Using OpenID Connect and OAuth, multiple RDAP servers can form a federation and clients can access any server in the federation by providing one credential registered with any OP in that federation. The OAuth authorization framework is designed for use with HTTP and thus can be used with RDAP.¶
This document uses the terms "client" and "server" as defined by RDAP [RFC7480].¶
This document uses the terms "Access Token", "Authorization Code", "Authorization Endpoint", "Authorization Grant", "Client Authentication", "Client Identifier", "Protected Resource", "Refresh Token", "Resource Owner", "Resource Server", and "Token Endpoint" defined by OAuth 2.0 [RFC6749]; the terms "Claim Name", "Claim Value", and "JSON Web Token (JWT)" defined by JSON Web Token (JWT) [RFC7519]; the term "ID Token" defined by OpenID Connect Core 1.0 [OIDCC]; and the term "JWT Access Token" defined by RFC 9068 [RFC9068]. Additional terms from Section 1.2 of the OpenID Connect Core specification are incorporated by reference.¶
This document uses the terms "remote" and "default" to describe the relationship between an RDAP server and the OpenID Providers that it interacts with. A "remote" OpenID Provider is one that is identified by the RDAP Client by providing either an Issuer Identifier or an End-User Identifier in a login request. Whether an Issuer Identifier or End-User Identifier can be provided in the login request for the purposes of selecting an OpenID Provider can be determined by retrieving the RDAP Server's OIDC configuration details (see Section 4.1). A "default" OpenID Provider is one that the RDAP Server will use when the RDAP Client does not provide an Issuer Identifier or an End-User Identifier in the login request.¶
This document uses the term "session" to describe a set of interactions between an RDAP client and an RDAP server during a given period of time. For session-oriented clients (see Section 3.1.2 and Section 5), the RDAP session is a typical HTTP session starting with a farv1_session/login request and ending with either a farv1_session/logout request or a timeout. For token-oriented clients (see Section 3.1.2 and Section 6), the RDAP session corresponds to the lifespan of an authorization obtained from an OP and the corresponding Access Token, including any refreshed Access Token.¶
Clients that delegate OIDC Authentication to an RDAP server as part of session-oriented interactions, and can accept and process HTTP cookies [RFC6265] to maintain the session, are known as "session-oriented" clients. This type of RDAP client performs the role of user agent [RFC9110]. An RDAP server performs the role of an OpenID Connect Core Relying Party (RP). A web browser used to send queries directly to an RDAP server is an example of a session-oriented client. Specifications for this type of client can be found in Section 5.¶
Clients that perform OIDC Authentication directly, taking the role of an RP in interactions with an OP and sending Access Tokens [RFC6749] to an RDAP server to authorize RDAP queries, are known as "token-oriented" clients. An RDAP server performs resource server [RFC6749] functions to verify the tokens received from the client, and RP functions to retrieve information from the OP as necessary to make access control decisions. A web browser running JavaScript received from a web service that sends queries to an RDAP server directly or through its back-end web service is an example of a token-oriented client. Specifications for this type of client can be found in Section 6.¶
Clients MAY operate as either session-oriented or token-oriented clients, but they MUST do so consistently during a given period of interaction with an OP. Servers SHOULD support both types of client to maximize interoperability, but MAY choose to support only one type of client as required by local policy or operating conditions. A server that does not support a particular client type will not support the protocol features (the data structures, path segments, parameters, and interactions) specified for that client type. Server signaling of supported client types is described in Section 4.1.¶
At a high level, RDAP authentication of a session-oriented client using OpenID Connect requires completion of the following steps:¶
The steps above can be described in a sequence diagram:¶
End OpenID RDAP RDAP User Provider Client Server | | | | | | |-----Help Query---->| | | | | | | |<---Help Response---| | | | | |-------Login Request------>| | | | | | | | |---Login Request--->| | | | | | |<-----Authentication Request------| | | | | | Credential--| | | |<--Request | | | | | | | |--Credential | | | | Response->| | | | | | | | |-----Authentication Response----->| | | | | | |<----------Token Request----------| | | | | | |-----------Token Response-------->| | | | | | |<----------Claim Request----------| | | | | | |-----------Claim Response-------->| | | | | | | |<--Login Response---| | | | | |<------Login Response------| | | | | | |----------RDAP Query------>| | | | | | | | |-----RDAP Query---->| | | | | | | |<---RDAP Response---| | | | | |<------RDAP Response-------| |
The RDAP server can then make identification, authorization, and access control decisions based on End-User identity information and local policies. Note that OpenID Connect describes different process flows for other types of clients, such as script-based or command line clients.¶
RDAP authentication of a token-oriented client using OpenID Connect requires completion of the following steps:¶
The steps above can be described in a sequence diagram:¶
End OpenID RDAP RDAP User Provider Server Client | | | | | | |<----Help Query-----| | | | | | | |---Help Response--->| | | | | |--------------------Login Request-------------->| | | | | | |<-----Authentication Request------| | | | | | Credential--| | | |<--Request | | | | | | | |--Credential | | | | Response->| | | | | | | | |-----Authentication Response----->| | | | | | |<----------Token Request----------| | | | | | |-----------Token Response-------->| | | | | | | | | |<-----------------Login Response----------------| | | | | |--------------------RDAP Query----------------->| | | | | | | |<----RDAP Query-----| | | | | | | Claim----| | | |<---Request | | | | | | | |---Claim | | | | Response-->| | | | | | | | |---RDAP Response--->| | | | | |<----------------RDAP Response------------------|
End-Users MAY present an identifier (an OpenID) issued by an OP to use OpenID Connect with RDAP. If the RDAP server supports a default OpenID Provider or provider discovery is not supported, the End-User identifier MAY be omitted. An OP SHOULD include support for the claims described in Section 3.1.5 to provide additional information needed for RDAP End-User authorization. OpenID Connect requires RPs to register with OPs to use OpenID Connect services for an End-User. The registration process is often completed using out-of-band methods, but it is also possible to use the automated method described by the "OpenID Connect Dynamic Client Registration" protocol [OIDCR]. The parties involved can use any method that is mutually acceptable.¶
An RDAP server/RP needs to be able to map an End-User's identifier to an OP. This can be accomplished using the OPTIONAL "OpenID Connect Discovery" protocol [OIDCD], but that protocol is not widely implemented. Out-of-band methods are also possible and can be more dependable. For example, an RP can support a limited number of OPs and maintain internal associations of those identifiers with the OPs that issued them.¶
Alternatively, if mapping of an End-User's identifier is not possible, or not supported by the RDAP server, the RDAP server SHOULD support explicit specification of a remote OP by the RDAP client in the form of a query parameter as described in Section 5.2.2. An RDAP server MUST provide information about its capabilities and supported OPs in the "help" query response in the "farv1_openidcConfiguration" data structure described in Section 4.1. An RDAP server/RP MUST support at least one of these methods of OP discovery.¶
Once the OP is known, an RP MUST form an Authentication Request and send it to the OP as described in Section 3 of the OpenID Connect Core protocol [OIDCC]. The authentication path followed (authorization, implicit, or hybrid) will depend on the Authentication Request response_type set by the RP. The remainder of the processing steps described here assume that the Authorization Code Flow is being used by setting "response_type=code" in the Authentication Request.¶
The benefits of using the Authorization Code Flow for authenticating a human user are described in Section 3.1 of the OpenID Connect Core protocol. The Implicit Flow is more commonly used by clients implemented in a web browser using a scripting language; it is described in Section 3.2 of the OpenID Connect Core protocol. At the time of this writing, the Implicit Flow is considered insecure and efforts are being made to deprecate the flow. The Hybrid Flow (described in Section 3.3 of the OpenID Connect Core protocol) combines elements of the Authorization and Implicit Flows by returning some tokens from the Authorization Endpoint and others from the Token Endpoint.¶
An Authentication Request can contain several parameters. REQUIRED parameters are specified in Section 3.1.2.1 of the OpenID Connect Core protocol [OIDCC]. Apart from these parameters, it is RECOMMENDED that the RP include the optional "login_hint" parameter in the request, with the value being that of the "farv1_id" query parameter of the End-User's RDAP "login" request, if provided. Passing the "login_hint" parameter allows a client to pre-fill login form information, so logging in can be more convenient for users. Other parameters MAY be included.¶
The OP receives the Authentication Request and attempts to validate it as described in Section 3.1.2.2 of the OpenID Connect Core protocol [OIDCC]. If the request is valid, the OP attempts to authenticate the End-User as described in Section 3.1.2.3 of the OpenID Connect Core protocol [OIDCC]. The OP returns an error response if the request is not valid or if any error is encountered.¶
After the End-User is authenticated, the OP MUST obtain consent from the End-User to release authorization information to the RDAP Server/RP. This process is described in Section 3.1.2.4 of the OpenID Connect Core protocol [OIDCC].¶
After obtaining an authorization result, the OP will send a response to the RP that provides the result of the authorization process using an Authorization Code. The RP MUST validate the response. This process is described in Sections 3.1.2.5 - 3.1.2.7 of the OpenID Connect Core protocol [OIDCC].¶
The RP sends a Token Request using the Authorization Grant to a Token Endpoint to obtain a Token Response containing an Access Token, ID Token, and an OPTIONAL Refresh Token. The RP MUST validate the Token Response. This process is described in Section 3.1.3.5 of the OpenID Connect Core protocol [OIDCC].¶
The set of claims can be retrieved by sending a request to a UserInfo Endpoint using the Access Token. The claims are returned in the ID Token. The process of retrieving claims from a UserInfo Endpoint is described in Section 5.3 of the OpenID Connect Core protocol [OIDCC].¶
OpenID Connect specifies a set of standard claims in Section 5.1 of the OpenID Connect Core protocol [OIDCC]. Additional claims for RDAP are described in Section 3.1.5.¶
OpenID Connect claims are pieces of information used to make assertions about an entity. Section 5 of the OpenID Connect Core protocol [OIDCC] describes a set of standard claims. Section 5.1.2 notes that additional claims MAY be used, and it describes a method to create them. The set of claims that are specific to RDAP are associated with an OAuth scope request parameter value (see Section 3.3 of RFC 6749 ([RFC6749])) of "rdap".¶
Communities of RDAP users and operators may wish to make and validate claims about a user's "need to know" when it comes to requesting access to a protected resource. For example, a law enforcement agent or a trademark attorney may wish to be able to assert that they have a legal right to access a protected resource, and a server operator may need to be able to receive and validate that claim. These needs can be met by defining and using an additional "rdap_allowed_purposes" claim.¶
The "rdap_allowed_purposes" claim identifies the purposes for which access to a protected resource can be requested by an End-User. Use of the "rdap_allowed_purposes" claim is OPTIONAL; processing of this claim is subject to server acceptance of the purposes, the trust level assigned to this claim by the server, and successful authentication of the End-User. Unrecognized purpose values MUST be ignored and the associated query MUST be processed as if the unrecognized purpose value was not present at all.¶
The "rdap_allowed_purposes" claim is represented as an array of case-sensitive StringOrURI values as specified in Section 2 of the JSON Web Token (JWT) specification ([RFC7519]). An example:¶
"rdap_allowed_purposes": ["domainNameControl","dnsTransparency"]¶
Individual purpose values are registered with IANA. Each entry in the registry contains the following fields:¶
Value: the purpose string value being registered. Value strings can contain upper case characters from "A" to "Z", lower case ASCII characters from "a" to "z", and the underscore ("_") character. Value strings contain at least one character and no more than 64 characters.¶
Description: a one- or two-sentence description of the meaning of the purpose value, how it might be used, and/or how it should be interpreted by clients and servers.¶
This registry is operated under the "Specification Required" policy defined in RFC 8126 ([RFC8126]). The set of initial values used to populate the registry as described in Section 9.3 are taken from the final report produced by the Expert Working Group on gTLD Directory Services chartered by the Internet Corporation for Assigned Names and Numbers (ICANN).¶
Communities of RDAP users and operators may wish to make and validate claims about a user's wish to not have their queries logged, tracked, or recorded. For example, a law enforcement agent may wish to assert that their queries are part of a criminal investigation and should not be tracked due to a risk of query exposure compromising the investigation, and a server operator may need to be able to receive and validate that claim. These needs can be met by defining and using an additional "do not track" claim.¶
The "do not track" ("rdap_dnt_allowed") claim can be used to identify an End-User that is authorized to perform queries without the End-User's association with those queries being logged, tracked, or recorded by the server. Client use of the "rdap_dnt_allowed" claim is OPTIONAL. Server operators MUST NOT log, track, or record any association of the query and the End-User's identity if the End-User is successfully identified and authorized, the "rdap_dnt_allowed" claim is present, the value of the claim is "true", and accepting the claim complies with local regulations regarding logging and tracking.¶
The "rdap_dnt_allowed" value is represented as a JSON boolean literal. An example:¶
rdap_dnt_allowed: true¶
No special query tracking processing is required if this claim is not present or if the value of the claim is "false". Use of this claim MUST be limited to End-Users who are granted "do not track" privileges in accordance with service policies and regulations. Specification of these policies and regulations is beyond the scope of this document.¶
As described in Section 3.1.4.1, an RDAP server MUST provide information about its capabilities and supported OPs in a "help" query response. This specification describes a new "farv1_openidcConfiguration" data structure that describes the OpenID Connect configuration and related extension features supported by the RDAP server. This data structure is returned to all client types.¶
The "farv1_openidcConfiguration" data structure is an object with the following members:¶
An RDAP server MUST set either the "sessionClientSupported" or "tokenClientSupported" value to "true". Both values MAY be set to "true" if an RDAP server supports both types of client.¶
The "providerDiscoverySupported" value has a direct impact on the use of the "farv1_id" query parameter described in Section 3.1.4.2 and Section 5.2.1. The value of "providerDiscoverySupported" MUST be "true" for an RDAP server to properly accept and process "farv1_id" query parameters. Similarly, The "issuerIdentifierSupported" value has a direct impact on the use of the "farv1_iss" query parameter described in Section 5.2.2. The value of "issuerIdentifierSupported" MUST be "true" for an RDAP server to properly accept and process "farv1_iss" query parameters.¶
An example of a "farv1_openidcConfiguration" data structure:¶
"farv1_openidcConfiguration": {
"sessionClientSupported": true,
"tokenClientSupported": true,
"dntSupported": false,
"providerDiscoverySupported": true,
"issuerIdentifierSupported": true,
"openidcProviders":
[
{
"iss": "https://idp.example.com",
"name": "Example IDP"
},
{
"iss": "https://accounts.example.net",
"name": "Login with EXAMPLE",
"additionalAuthorizationQueryParams": {
"kc_idp_hint": "examplePublicIDP"
}
},
{
"iss": "https://auth.nic.example/auth/realms/rdap",
"name": "Default OP for the Example RDAP server",
"default": true
}
]
}
This specification describes two OPTIONAL query parameters for use with RDAP queries that request access to information associated with protected resources:¶
One or both parameters MAY be added to an RDAP request URI using the syntax described in Section 3.4 of RFC 3986 [RFC3986].¶
This query is represented as a "key=value" pair using a key value of "farv1_qp" and a value component that contains a single query purpose string from the set of allowed purposes associated with the End-User's identity (see Section 3.1.5.1). If present, the server SHOULD compare the value of the parameter to the "rdap_allowed_purposes" claim values associated with the End-User's identity and ensure that the requested purpose is present in the set of allowed purposes. The RDAP server MAY choose to ignore both requested purpose and the "rdap_allowed_purposes" claim values if they are inconsistent with local server policy. The server MUST return an HTTP 403 (Forbidden) response if the requested purpose is not an allowed purpose. If the "farv1_qp" parameter is not present, the server MUST process the query and make an access control decision based on any other information known to the server about the End-User and the information they are requesting. For example, a server MAY treat the request as one performed by an unidentified or unauthenticated user and return either an error or an appropriate subset of the available data. An example domain query using the "farv1_qp" query parameter:¶
https://example.com/rdap/domain/example.com?farv1_qp=legalActions¶
This query is represented as a "key=value" pair using a key value of "farv1_dnt" and a value component that contains a single boolean value. A value of "true" indicates that the End-User is requesting that their query is not tracked or logged in accordance with server policy. A value of "false" indicates that the End-User is accepting that their query can be tracked or logged in accordance with server policy. The server MUST return an HTTP 403 (Forbidden) response if the server is unable to perform the action requested by this query parameter. An example domain query using the "farv1_dnt" query parameter:¶
https://example.com/rdap/domain/example.com?farv1_dnt=true¶
Unrecognized query parameters MUST be ignored. An RDAP server that processes an authenticated query MUST determine if the End-User identification information is associated with an OP that is recognized and supported by the server. RDAP servers MUST reject queries that include identification information that is not associated with a supported OP by returning an HTTP 400 (Bad Request) response. An RDAP server that receives a query containing identification information associated with a recognized OP MUST perform the steps required to authenticate the user with the OP, process the query, and return an RDAP response that is appropriate for the End-User's level of authorization and access.¶
This specification adds the following features to RDAP that are commonly used by session-oriented clients:¶
This specification describes two new data structures that are used to return information to a session-oriented client: a "farv1_session" data structure that contains information that describes an established session, and a "farv1_deviceInfo" data structure that contains information that describes an active attempt to establish a session on a UI-constrained device.¶
The "farv1_session" data structure is an object that contains the following members:¶
"sessionInfo": an OPTIONAL object that contains two members:¶
An example of a "farv1_session" data structure:¶
"farv1_session": {
"userID": "user.idp.example",
"iss": "https://idp.example.com",
"userClaims": {
"sub": "103892603076825016132",
"name": "User Person",
"given_name": "User",
"family_name": "Person",
"picture": "https://lh3.example.com/a-/AOh14=s96-c",
"email": "user@example.com",
"email_verified": true,
"locale": "en",
"rdap_allowed_purposes": [
"domainNameControl",
"personalDataProtection"
],
"rdap_dnt_allowed": false
},
"sessionInfo": {
"tokenExpiration": 3599,
"tokenRefresh": true
}
}
The flow described in Section 3.1.4 requires an End-User to interact with a server using a user interface that can process HTTP. This will not work well in situations where the client is automated or an End-User is using a command line user interface such as curl or wget. This limitation can be addressed using a web browser on a second device. The information that needs to be entered using the web browser is contained in the "farv1_deviceInfo" data structure.¶
The "farv1_deviceInfo" data structure is an object that contains three members:¶
An example of a "farv1_deviceInfo" data structure:¶
"farv1_deviceInfo": {
"verification_url": "https://www.example.com/device",
"user_code": "NJJQ-GJFC",
"device_code": "AH-1ng2ezu",
"expires_in": "1800"
}
Client authentication is requested by sending a "farv1_session/login" request to an RDAP server. If the RDAP server supports only remote OpenID Providers, the "farv1_session/login" request MUST include at least one of an End-User Identifier or an OP Issuer Identifier.¶
The server sets an HTTP cookie as described in RFC 6265 [RFC6265] when the "farv1_session/login" request is received and processed successfully. The client MUST include the session cookie received from the server in any RDAP request within the scope of that session, including "farv1_session/refresh", "farv1_session/status" and "farv1_session/logout". A "farv1_session/login" followed by another "farv1_session/login" that does not include an HTTP cookie MUST start a new session on the server that includes a new cookie. A server that receives a "farv1_session/login" followed by another "farv1_session/login" that includes an HTTP cookie MUST return an HTTP 409 (Conflict) response.¶
To help reduce the risk of resource starvation, a server MAY reject a "farv1_session/login" request and refuse to start a new session by returning an HTTP 409 (Conflict) response if a server-side maximum number of concurrent sessions per user exists and the client exceeds that limit. Additionally, an active session MAY be removed by the server due to timeout expiration or because a maximum session lifetime has been exceeded. Clients SHOULD proactively monitor the "tokenExpiration" value associated with an active session and refresh the session as appropriate to provide a positive user experience.¶
The End-User identifier is delivered using one of two methods: by adding a query component to an RDAP request URI using the syntax described in Section 3.4 of RFC 3986 [RFC3986], or by including an HTTP "Authorization" request header for the Basic authentication scheme as described in RFC 7617 [RFC7617]. Clients can use either of these methods to deliver the End-User identifier to a server that supports remote OpenID Providers and provider discovery. Servers that support remote OpenID Providers and provider discovery MUST accept both methods. If the RDAP server supports a default OpenID Provider or provider discovery is not supported, the End-User identifier MAY be omitted.¶
The query parameter used to deliver the End-User identifier is represented as an OPTIONAL "key=value" pair using a key value of "farv1_id" and a value component that contains the client identifier issued by an OP. An example for client identifier "user.idp.example":¶
https://example.com/rdap/farv1_session/login?farv1_id=user.idp.example¶
The authorization header for the Basic authentication scheme contains a Base64-encoded representation of the client identifier issued by an OP. No password is provided. An example for client identifier "user.idp.example":¶
https://example.com/rdap/farv1_session/login¶
Authorization: Basic dXNlci5pZHAuZXhhbXBsZQ==¶
An example for use with a default OpenID Provider:¶
https://example.com/rdap/farv1_session/login¶
The OP's Issuer Identifier is delivered by adding a query component to an RDAP request URI using the syntax described in Section 3.4 of RFC 3986 [RFC3986]. If the RDAP server supports a default OpenID Provider, the Issuer Identifier MAY be omitted.¶
The query parameter used to deliver the OP's Issuer Identifier is represented as an OPTIONAL "key=value" pair using a key value of "farv1_iss" and a value component that contains the Issuer Identifier associated with an OP. An RDAP server MAY accept Issuer Identifiers not specified in the "farv1_openidcConfiguration" data structure and MAY also decide to accept specific Issuer Identifiers only from specific clients.¶
An example for Issuer Identifier "https://idp.example.com":¶
https://example.com/rdap/farv1_session/login?farv1_iss=https%3A%2F%2Fidp.example.com¶
The response to this request MUST be a valid RDAP response, per RFC 9083 [RFC9083]. It MUST NOT include any members that relate to a specific RDAP object type (e.g. "events", "status"). In addition, the response MAY include an indication of the requested operation's success or failure in the "notices" data structure. If successful, the response MUST include a "farv1_session" data structure that includes a "sessionInfo" object and an OPTIONAL "userClaims" object. If unsuccessful, the response MUST include a "farv1_session" data structure that omits the "userClaims" and "sessionInfo" objects.¶
An example of a successful "farv1_session/login" response:¶
{
"rdapConformance": [
"farv1"
],
"lang": "en-US",
"notices": [
{
"title": "Login Result",
"description": [
"Login succeeded"
]
}
],
"farv1_session": {
"userID": "user.idp.example",
"iss": "https://idp.example.com",
"userClaims": {
"sub": "103892603076825016132",
"name": "User Person",
"given_name": "User",
"family_name": "Person",
"picture": "https://lh3.example.com/a-/AOh14=s96-c",
"email": "user@example.com",
"email_verified": true,
"locale": "en",
"rdap_allowed_purposes": [
"domainNameControl",
"personalDataProtection"
],
"rdap_dnt_allowed": false
},
"sessionInfo": {
"tokenExpiration": 3599,
"tokenRefresh": true
}
}
}
An example of a failed "farv1_session/login" response:¶
{
"rdapConformance": [
"farv1"
],
"lang": "en-US",
"notices": [
{
"title": "Login Result",
"description": [
"Login failed"
]
}
],
"farv1_session": {
"userID": "user.idp.example",
"iss": "https://idp.example.com"
}
}
The "OAuth 2.0 Device Authorization Grant" [RFC8628] provides an OPTIONAL method to request user authorization from devices that have an Internet connection, but lack a suitable browser for a more traditional OAuth flow. This method requires an End-User to use a second device (such as a smart telephone) that has access to a web browser for entry of a code sequence that is presented on the UI-constrained device.¶
Client authentication is requested by sending a "farv1_session/device" request to an RDAP server. If the RDAP server supports only remote OpenID Providers, the "farv1_session/device" request MUST include either an End-User identifier as described in Section 5.2.1 or an OP Issuer Identifier as described in Section 5.2.2.¶
An example using wget for client identifier "user.idp.example":¶
wget -qO- \ "https://example.com/rdap/farv1_session/device\ ?farv1_id=user.idp.example"
The authorization header for the Basic authentication scheme contains a Base64-encoded representation of the client identifier issued by an OP. No password is provided.¶
An example using curl and an authorization header:¶
curl -H "Authorization: Basic dXNlci5pZHAuZXhhbXBsZQ=="\ "https://example.com/rdap/farv1_session/device"
The response to this request MUST be a valid RDAP response, per RFC 9083 [RFC9083]. It MUST NOT include any members that relate to a specific RDAP object type (e.g. "events", "status"). In addition, the response MAY include an indication of the requested operation's success or failure in the "notices" data structure, and, if successful, a "farv1_deviceInfo" data structure.¶
An example of a "farv1_session/device" response:¶
{
"rdapConformance": [
"farv1"
],
"lang": "en-US",
"notices": [
{
"title": "Device Login Result",
"description": [
"Login succeeded"
]
}
],
"farv1_deviceInfo": {
"verification_url": "https://www.example.com/device",
"user_code": "NJJQ-GJFC",
"device_code": "AH-1ng2ezu",
"expires_in": 1800
}
}
After successful processing of the "farv1_session/device" request, the client MUST send a "farv1_session/devicepoll" request to the RDAP server to continue the login process. This request performs the polling function described in RFC 8628 [RFC8628], allowing the RDAP server to wait for the End-User to enter the information returned from the "farv1_session/device" request using the interface on their second device. After the End-User has completed that process, or if the process fails or times out, the OP will respond to the polling requests with an indication of success or failure. If the RDAP server supports only remote OpenID Providers, the "farv1_session/devicepoll" request MUST include either an End-User identifier as described in Section 5.2.1 or an OP Issuer Identifier as described in Section 5.2.2.¶
The "farv1_session/devicepoll" request MUST also include a "farv1_dc" query parameter. The query parameter is represented as an OPTIONAL "key=value" pair using a key value of "farv1_dc" and a value component that contains the value of the device_code that was returned in the response to the "farv1_session/device" request.¶
An example using wget:¶
wget -qO- --keep-session-cookies --save-cookies cookie.txt\ "https://example.com/rdap/farv1_session/devicepoll\ ?farv1_id=user.idp.example&farv1_dc=AH-1ng2ezu"
An example using curl:¶
curl -c cookie.txt\ "https://example.com/rdap/farv1_session/devicepoll\ ?farv1_id=user.idp.example&farv1_dc=AH-1ng2ezu"
The response to this request MUST use the response structures described in Section 5.2. RDAP query processing can continue normally on the UI-constrained device once the device polling process has been completed successfully.¶
Clients MAY send a query to an RDAP server to determine the status of an existing login session using a "farv1_session/status" path segment. An example "farv1_session/status" request:¶
https://example.com/rdap/farv1_session/status¶
The response to this request MUST be a valid RDAP response, per RFC 9083 [RFC9083]. It MUST NOT include any members that relate to a specific RDAP object type (e.g. "events", "status"). In addition, the response MAY include an indication of the requested operation's success or failure in the "notices" data structure. If the operation is successful, and an active session exists, the response MUST include a "farv1_session" data structure that includes a "sessionInfo" object and an OPTIONAL "userClaims" object. If the operation is unsuccessful, or if no active session exists, the response MUST NOT include a "farv1_session" object.¶
An example of a "farv1_session/status" response for an active session:¶
{
"rdapConformance": [
"farv1"
],
"lang": "en-US",
"notices": [
{
"title": "Session Status Result",
"description": [
"Session status succeeded"
]
}
],
"farv1_session": {
"userID": "user.idp.example",
"iss": "https://idp.example.com",
"userClaims": {
"sub": "103892603076825016132",
"name": "User Person",
"given_name": "User",
"family_name": "Person",
"picture": "https://lh3.example.com/a-/AOh14=s96-c",
"email": "user@example.com",
"email_verified": true,
"locale": "en",
"rdap_allowed_purposes": [
"domainNameControl",
"personalDataProtection"
],
"rdap_dnt_allowed": false
},
"sessionInfo": {
"tokenExpiration": 3490,
"tokenRefresh": true
}
}
}
If the operation is successful, and an active session does not exist, the response MAY note the lack of an active session in the "notices" data structure. The "farv1_session" data structure MUST be omitted.¶
An example of a "farv1_session/status" response with no active session:¶
{
"rdapConformance": [
"farv1"
],
"lang": "en-US",
"notices": [
{
"title": "Session Status Result",
"description": [
"Session status succeeded",
"No active session"
]
}
]
}
Clients MAY send a request to an RDAP server to refresh, or extend, an existing login session using a "farv1_session/refresh" path segment. The RDAP server MAY attempt to refresh the Access Token associated with the current session as part of extending the session for a period of time determined by the RDAP server. As described in RFC 6749 [RFC6749], OP support for refresh tokens is OPTIONAL. An RDAP server MUST determine if the OP supports token refresh and process the refresh request by either requesting refresh of the Access Token or by returning a response that indicates that token refresh is not supported by the OP in the "notices" data structure. An example "farv1_session/refresh" request:¶
https://example.com/rdap/farv1_session/refresh¶
The response to this request MUST be a valid RDAP response, per RFC 9083 [RFC9083]. It MUST NOT include any members that relate to a specific RDAP object type (e.g. "events", "status"). In addition, the response MAY include an indication of the requested operation's success or failure in the "notices" data structure. The response MUST include a "farv1_session" data structure that includes a "sessionInfo" object and an OPTIONAL "userClaims" object. If unsuccessful, but an active session exists, the response MUST include a "farv1_session" data structure that includes a "sessionInfo" object and an OPTIONAL "userClaims" object. If unsuccessful, and no active session exists, the response MUST omit the "farv1_session" data structure.¶
An example of a successful "farv1_session/refresh" response:¶
{
"rdapConformance": [
"farv1"
],
"lang": "en-US",
"notices": [
{
"title": "Session Refresh Result",
"description": [
"Session refresh succeeded",
"Token refresh succeeded."
]
}
],
"farv1_session": {
"userID": "user.idp.example",
"iss": "https://idp.example.com",
"userClaims": {
"sub": "103892603076825016132",
"name": "User Person",
"given_name": "User",
"family_name": "Person",
"picture": "https://lh3.example.com/a-/AOh14=s96-c",
"email": "user@example.com",
"email_verified": true,
"locale": "en",
"rdap_allowed_purposes": [
"domainNameControl",
"personalDataProtection"
],
"rdap_dnt_allowed": false
},
"sessionInfo": {
"tokenExpiration": 3599,
"tokenRefresh": true
}
}
}
Alternatively, an RDAP server MAY attempt to refresh an Access Token upon receipt of a query if the Access Token associated with an existing session has expired and the corresponding OP supports token refresh. The default RDAP server behavior is described in the "implicitTokenRefreshSupported" value that's included in the "farv1_openidcConfiguration" data structure (see Section 4.1).¶
If the value of "implicitTokenRefreshSupported" is "true", the client MAY either explicitly attempt to refresh the session using the "farv1_session/refresh" query, or it MAY depend on the RDAP server to attempt to refresh the session as necessary when an RDAP query is received by the server. In this case, a server MUST attempt to refresh the Access Token upon receipt of a query if the Access Token associated with an existing session has expired and the corresponding OP supports token refresh. Servers MUST return an HTTP 401 (Unauthorized) response to a query if an attempt to implicitly refresh an existing session fails.¶
If the value of "implicitTokenRefreshSupported" is "false", the client MUST explicitly attempt to refresh the session using the "farv1_session/refresh" query to extend an existing session. If a session cannot be extended for any reason, the client MUST establish a new session to continue authenticated query processing by submitting a "farv1_session/login" query. If the OP does not support token refresh, the client MUST submit a new "farv1_session/login" request to establish a new session once an Access Token has expired.¶
Clients SHOULD NOT send a "farv1_session/refresh" request in the absence of an active login session because the request conflicts with the current state of the server. Servers MUST return an HTTP 409 (Conflict) response if a "farv1_session/refresh" request is received in the absence of a session cookie.¶
Clients MAY send a request to an RDAP server to terminate an existing login session. Termination of a session is requested using a "farv1_session/logout" path segment. Access and refresh tokens can be revoked during the "farv1_session/logout" process as described in RFC 7009 [RFC7009] if supported by the OP (token revocation endpoint support is OPTIONAL per RFC 8414 [RFC8414]). If supported, this feature SHOULD be used to ensure that the tokens are not mistakenly associated with a future RDAP session. Alternatively, an RDAP server MAY attempt to logout from the OP using the "OpenID Connect RP-Initiated Logout" protocol ([OIDCL]) if that protocol is supported by the OP. In any case, an RDAP server SHOULD invalidate the HTTP cookie associated with the session as part of terminating the session.¶
An example "farv1_session/logout" request:¶
https://example.com/rdap/farv1_session/logout¶
The response to this request MUST be a valid RDAP response, per RFC 9083 [RFC9083]. It MUST NOT include any members that relate to a specific RDAP object type (e.g. "events", "status"). In addition, the response MAY include an indication of the requested operation's success or failure in the "notices" data structure. The "notices" data structure MAY include an indication of the success or failure of any attempt to logout from the OP or to revoke the tokens issued by the OP.¶
An example of a "farv1_session/logout" response:¶
{
"rdapConformance": [
"farv1"
],
"lang": "en-US",
"notices": [
{
"title": "Logout Result",
"description": [
"Logout succeeded"
"Provider logout failed: Not supported by provider.",
"Token revocation successful."
]
}
]
}
In the absence of a "logout" request, an RDAP session MUST be terminated by the RDAP server after a server-defined period of time. The server SHOULD also take appropriate steps to ensure that the tokens associated with the terminated session cannot be reused. This SHOULD include revoking the tokens or logging out from the OP if either operation is supported by the OP.¶
The requests described in this document are typically performed in a specific sequence: "farv1_session/login" (or the related "farv1_session/device" and "farv1_session/devicepoll" requests) to start a session, "farv1_session/status" and/or "farv1_session/refresh" to manage a session, and "farv1_session/logout" to end a session. If a client sends a "farv1_session/status", "farv1_session/refresh", or "farv1_session/logout" request in the absence of a session cookie, the server MUST return an HTTP 409 (Conflict) error.¶
A client can end a session explicitly by sending a "farv1_session/logout" request to the RDAP server. A session can also be ended implicitly by the server after a server-defined period of time. The status of a session can be determined at any time by sending a "farv1_session/status" query to the RDAP server.¶
An RDAP server MUST maintain session state information for the duration of an active session. This is commonly done using HTTP cookies as described in RFC 6265 [RFC6265]. Doing so allows End-User to submit queries without having to explicitly identify and authenticate themselves for every query.¶
An RDAP server can receive queries that include a session cookie where the associated session has expired or is otherwise unavailable (e.g. due to the user requesting explicit logout for the associated session). The server MUST return an HTTP 401 (Unauthorized) error in response to such queries.¶
This specification adds additional processing steps for token-oriented clients as described in this section and Section 3.1.3. It does not define additional data structures or RDAP-specific protocol parameters specifically for token-oriented clients.¶
Clients identify and authenticate End-Users by exchanging information with an OP that is recognized by the RDAP server as described in Section 3.1.4.2, Section 3.1.4.3, and Section 3.1.4.4. A client SHOULD append the "additionalAuthorizationQueryParams" values retrieved from the "openidcProviders" array described in Section 4.1 to the Authorization Endpoint URL when requesting authorization from the OP. Once these processes are completed successfully, the client can request tokens from the OP as described in Section 3.1.4.5. The OP SHOULD include the RDAP server's client_id in the "aud" claim value of an issued ID token. The RDAP server MAY choose to ignore the value of the "aud" claim or exchange the token as described in Section 6.4. With these steps completed, the Access Token received from the OP can be passed to an RDAP server in an HTTP "Authorization" request header [RFC6750] for RDAP queries that require End-User identification, authentication, and authorization.¶
An RDAP server that receives a bearer token in an HTTP "Authorization" request header as part of an RDAP object query MUST validate the token in accordance with local policy and confirm that the token is a legitimate Access Token. Once validated, the Access Token SHOULD be used to retrieve the claims associated with the End-User's identity (including claims associated with the "rdap" scope) as described in Section 3.1.4.6. The RDAP server can then evaluate the End-User's identity information to determine the End-User's authorization level and process the query in accordance with server policies. A client MUST include the "farv1_iss" query parameter and issuer identifier value with an RDAP query if the token was issued by a remote OP.¶
An RDAP server MUST validate a received Access Token prior to using that token for access control purposes. Validation MAY include token introspection [RFC7662] using the issuing OP, or analysis of the values included in a JWT Access Token. Once an Access Token is validated, an RDAP server MAY use that token to request user claims from the issuing OP.¶
There are performance considerations associated with the process of validating a token and requesting user claims as part of processing every received RDAP query. An RDAP server MAY cache validated information and use that cached information to reduce the amount of time needed to process subsequent RDAP queries associated with the same Access Token as long as the token has not expired. The client SHOULD monitor the token expiration time and refresh the token as needed.¶
ID tokens include an "aud" (audience) claim that contains the OAuth 2.0 client_id of the RP as an audience value. In some operational scenarios (such as a client that is providing a proxy service), an RP can receive tokens with an "aud" value that does not include the RP's client_id. These tokens might not be trusted by the RP, and the RP might refuse to accept the tokens. This situation can be remedied by having the RP exchange these tokens with the OP for a set of trusted tokens that reset the "aud" claim. This token exchange protocol is described in RFC 8693 [RFC8693]. This issue is not visible to the RDAP client and should be managed by the OpenID implementation used by the RDAP server.¶
Once an RDAP session is active, an RDAP server MUST determine if the End-User is authorized to perform any queries that are received during the duration of the session. This MAY include rejecting queries outright, and it MAY include omitting or otherwise redacting information that the End-User is not authorized to receive. Specific processing requirements are beyond the scope of this document.¶
RDAP responses that contain values described in this document MUST indicate conformance with this specification by including an rdapConformance ([RFC9083]) value of "farv1" (Federated Authentication for RDAP version 1). The information needed to register this value in the RDAP Extensions Registry is described in Section 9.1.¶
Example rdapConformance structure with extension specified:¶
"rdapConformance" :
[
"rdap_level_0",
"farv1"
]
IANA is requested to register the following value in the RDAP Extensions Registry:¶
IANA is requested to register the following values in the JSON Web Token Claims Registry:¶
IANA is requested to create a new protocol registry to manage RDAP query purpose values. This registry should be named "Registration Data Access Protocol (RDAP) Query Purpose Values" and should appear under the "Registration Data Access Protocol (RDAP)" section of IANA's protocol registries. The information to be registered and the procedures to be followed in populating the registry are described in Section 3.1.5.1.¶
Section at http://www.iana.org/protocols: Registration Data Access Protocol (RDAP)¶
Name of registry: Registration Data Access Protocol (RDAP) Query Purpose Values¶
Registration Procedure: Specification Required¶
Reference: This document¶
Required information: See Section 3.1.5.1.¶
Review process: "Specification Required" as described in RFC 8126 [RFC8126].¶
Size, format, and syntax of registry entries: See Section 3.1.5.1.¶
Initial assignments and reservations:¶
-----BEGIN FORM-----¶
-----END FORM-----¶
-----BEGIN FORM-----¶
-----END FORM-----¶
-----BEGIN FORM-----¶
-----END FORM-----¶
-----BEGIN FORM-----¶
-----END FORM-----¶
-----BEGIN FORM-----¶
-----END FORM-----¶
-----BEGIN FORM-----¶
-----END FORM-----¶
-----BEGIN FORM-----¶
-----END FORM-----¶
-----BEGIN FORM-----¶
-----END FORM-----¶
-----BEGIN FORM-----¶
-----END FORM-----¶
-----BEGIN FORM-----¶
-----END FORM-----¶
-----BEGIN FORM-----¶
-----END FORM-----¶
NOTE: Please remove this section and the reference to RFC 7942 prior to publication as an RFC.¶
This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a proposal described in RFC 7942 [RFC7942]. The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist.¶
According to RFC 7942, "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit".¶
Version -09 of this specification introduced changes that are incompatible with earlier implementations. Implementations that are consistent with this specification will be added as they are identified.¶
Description: This implementation includes support for domain registry RDAP queries using live data from the .cc and .tv country code top-level domains and the .career generic top-level domain. Three access levels are provided based on the authenticated identity of the client:¶
Security considerations for RDAP can be found in RFC 7481 [RFC7481]. Security considerations for OpenID Connect Core [OIDCC] and OAuth 2.0 [RFC6749] can be found in their reference specifications. OpenID Connect defines optional mechanisms for robust signing and encryption that can be used to provide data integrity and data confidentiality services as needed. Additionally, the practices described in RFC 8996 [RFC8996] MUST be followed when the Transport Layer Security (TLS) protocol is used.¶
As described in Section 3.1.4.2, the OAuth 2.0 Implicit Flow [RFC6749] is considered insecure and efforts are being made to deprecate the flow. It SHOULD NOT be used.¶
Some of the responses described in this specification return information to a client from an RDAP server that is intended to help the client match responses to queries and manage sessions. Some of that information, such as the "userClaims" described in Section 5.1.1, can be personally identifiable and considered sensitive if disclosed to unauthorized parties. An RDAP server operator SHOULD develop policies for information disclosure to ensure that personally identifiable information is disclosed only to clients that are authorized to process that information.¶
Having completed the client identification, authorization, and validation process, an RDAP server can make access control decisions based on a comparison of client-provided information (such as the set of "userClaims" described in Section 5.1.1) and local policy. For example, a client who provides an email address (and nothing more) might be entitled to receive a subset of the information that would be available to a client who provides an email address, a full name, and a stated purpose. Development of these access control policies is beyond the scope of this document.¶
The author would like to acknowledge the following individuals for their contributions to the development of this document: Julien Bernard, Marc Blanchet, Tom Harrison, Russ Housley, Jasdip Singh, Rhys Smith, Jaromir Talir, Rick Wilhelm, and Alessandro Vesely. In addition, the Verisign Registry Services Lab development team of Joseph Harvey, Andrew Kaizer, Sai Mogali, Anurag Saxena, Swapneel Sheth, Nitin Singh, and Zhao Zhao provided critical "proof of concept" implementation experience that helped demonstrate the validity of the concepts described in this document.¶
Pawel Kowalik and Mario Loffredo provided significant text contributions that led to welcome improvements in several sections of this document. Their contributions are greatly appreciated.¶