Skip to main content

Federated Authentication for the Registration Data Access Protocol (RDAP) using OpenID Connect

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author Scott Hollenbeck
Last updated 2019-03-02 (Latest revision 2018-08-29)
Replaces draft-hollenbeck-weirds-rdap-openid
Replaced by draft-ietf-regext-rdap-openid
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-regext-rdap-openid
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


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.


Scott Hollenbeck

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)