OAuth 2.0 Assisted Token
draft-ideskog-assisted-token-00

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Authors Jacob Ideskog  , Travis Spencer 
Last updated 2018-09-19 (latest revision 2018-03-18)
Stream (None)
Formats
Expired & archived
pdf htmlized bibtex
Additional Resources
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
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-ideskog-assisted-token-00.txt

Abstract

The OAuth 2.0 authorization flow for Single Page Applications (SPAs), often referred to as the assisted token flow, enables OAuth clients to request user authorization written in scripting languages, like JavaScript, with a simplified integration compared to the implicit grant type flow. Communication does not rely on redirection of the user agent, but instead leverages HTML's iframe element, child windows, and the postMessage interface. This communication is done using an additional endpoint, the assisted token endpoint, which this document defines.

Authors

Jacob Ideskog (jacob@curity.io)
Travis Spencer (travis@curity.io)

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