Reciprocal OAuth
draft-ietf-oauth-reciprocal-04

Document Type Expired Internet-Draft (oauth WG)
Last updated 2020-02-02 (latest revision 2019-08-01)
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream WG state In WG Last Call
Document shepherd Rifaat Shekh-Yusef
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>

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-04.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 (dick.hardt@gmail.com)

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