Skip to main content

Reciprocal OAuth
draft-ietf-oauth-reciprocal-01

The information below is for an old version of the document.
Document Type Expired Internet-Draft (oauth WG)
Author Dick Hardt
Last updated 2019-04-22 (Latest revision 2018-10-19)
Stream Internet Engineering Task Force (IETF)
Formats
Expired & archived
plain text xml htmlized pdfized bibtex
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Expired
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)
This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at:
https://www.ietf.org/archive/id/draft-ietf-oauth-reciprocal-01.txt

Abstract

There are times when a user has a pair of protected resources that would like to request access to each other. While OAuth flows typically enable the user to grant a client access to a protected resource, granting the inverse access requires an additional flow. Reciprocal OAuth enables a more seamless experience for the user to grant access to a pair of protected resources.

Authors

Dick Hardt

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