Skip to main content

RTCWEB Generic Identity Provider Interface

Document Type Expired Internet-Draft (individual)
Expired & archived
Author Eric Rescorla
Last updated 2012-09-13 (Latest revision 2012-03-12)
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
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:


Security for RTCWEB communications requires that the communicating endpoints be able to authenticate each other. While authentication may be mediated by the calling service, there are settings in which this is undesirable. This document describes a generic mechanism for leveraging existing identity providers (IdPs) such as BrowserID or OAuth to provide this authentication service.


Eric Rescorla

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