Skip to main content

Federated Authentication for the Registration Data Access Protocol (RDAP) Using OpenID Connect
RFC 9560

Revision differences

Document history

Date By Action
2026-05-20
(System) Changed metadata: changed keywords to '['RDAP', 'Federated', 'Authentication']' from '[]'
2026-05-20
(System) Metadata update from RFC Editor
2026-05-20
(System) Changed author "S. Hollenbeck": changed name from "Scott Hollenbeck" to "S. Hollenbeck", cleared country (was "USA")
2026-05-20
(System) Metadata update from RFC Editor
2024-04-26
(System) IANA registries were updated to include RFC9560
2024-04-26
(System)
Received changes through RFC Editor sync (created document RFC 9560, created became rfc relationship between draft-ietf-regext-rdap-openid and RFC 9560, set title to 'Federated …
Received changes through RFC Editor sync (created document RFC 9560, created became rfc relationship between draft-ietf-regext-rdap-openid and RFC 9560, set title to 'Federated Authentication for the Registration Data Access Protocol (RDAP) Using OpenID Connect', set abstract to 'The Registration Data Access Protocol (RDAP) provides Representational State Transfer (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.', set pages to 40, set standardization level to Proposed Standard, added RFC published event at 2024-04-26)
2024-04-26
(System) RFC published