> -----Original Message----- > From: regext <regext-boun...@ietf.org> On Behalf Of internet- > dra...@ietf.org > Sent: Friday, May 31, 2019 2:11 PM > To: i-d-annou...@ietf.org > Cc: regext@ietf.org > Subject: [EXTERNAL] [regext] I-D Action: draft-ietf-regext-rdap-openid-02.txt > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Registration Protocols Extensions WG of the > IETF. > > Title : Federated Authentication for the Registration Data > Access > Protocol (RDAP) using OpenID Connect > Author : Scott Hollenbeck > Filename : draft-ietf-regext-rdap-openid-02.txt > Pages : 25 > Date : 2019-05-31 > > Abstract: > 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. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-openid/
I got the Access and ID tokens swapped in the last update. This version correctly describes the Access token as the bearer token. Scott _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
