Skip to main content

This is an Internet-draft
draft-hardt-mutual-oauth-00

Document Type Replaced Internet-Draft (individual)
Author Dick Hardt
Last updated 2017-10-30
Replaced by draft-hardt-oauth-mutual
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text xml htmlized pdfized bibtex
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-hardt-oauth-mutual
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-hardt-mutual-oauth-00.txt

Abstract

There are times when a user has a pair 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. Mutual OAuth enables a more seemless 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.)