The XAuth Protocol
draft-hardt-xauth-protocol-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2020-01-30
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                      D. Hardt, Ed.
Internet-Draft                                                SignIn.Org
Intended status: Standards Track                         29 January 2020
Expires: 1 August 2020

                           The XAuth Protocol
                     draft-hardt-xauth-protocol-01

Abstract

   Client software often desires resources or identity claims that are
   managed independent of the client.  This protocol allows a user and/
   or resource owner to delegate resource authorization and/or release
   of identity claims to an authorization server.  Client software can
   then request access to resources and/or identity claims by calling
   the authorization server.  The authorization server acquires consent
   and authorization from the user and/or resource owner if required,
   and then returns the authorization and identity claims that were
   approved.  This protocol can be extended to support alternative
   client authentication mechanisms, authorizations, claims, and
   interactions.

   [Editor: suggestions on how to improve this are welcome!]

   [Editor: suggestions for other names than XAuth are welcome!]

Note to Readers

   Source for this draft and an issue tracker can be found at
   https://github.com/dickhardt/hardt-xauth-protocol
   (https://github.com/dickhardt/hardt-xauth-protocol).

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Hardt                     Expires 1 August 2020                 [Page 1]
Internet-Draft             The XAuth Protocol               January 2020

   This Internet-Draft will expire on 1 August 2020.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Simplified BSD License text
   as described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Protocol  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Parties . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Handles . . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.3.  Reused Terms  . . . . . . . . . . . . . . . . . . . . . .   5
     2.4.  Sequence  . . . . . . . . . . . . . . . . . . . . . . . .   6
   3.  AS Request JSON . . . . . . . . . . . . . . . . . . . . . . .   8
     3.1.  Top Level Attributes  . . . . . . . . . . . . . . . . . .  11
     3.2.  "client" Object . . . . . . . . . . . . . . . . . . . . .  11
     3.3.  "user" Object . . . . . . . . . . . . . . . . . . . . . .  12
     3.4.  "authentication" Object . . . . . . . . . . . . . . . . .  13
     3.5.  "authorizations" Object . . . . . . . . . . . . . . . . .  13
     3.6.  "claims" Object . . . . . . . . . . . . . . . . . . . . .  14
     3.7.  Authorization Types . . . . . . . . . . . . . . . . . . .  14
   4.  Interaction Response JSON . . . . . . . . . . . . . . . . . .  14
     4.1.  "user" Object . . . . . . . . . . . . . . . . . . . . . .  15
     4.2.  "interaction" Object  . . . . . . . . . . . . . . . . . .  15
     4.3.  "authorization" Object  . . . . . . . . . . . . . . . . .  16
     4.4.  "authentication" Object . . . . . . . . . . . . . . . . .  16
   5.  Interaction Types . . . . . . . . . . . . . . . . . . . . . .  16
     5.1.  "popup" Type  . . . . . . . . . . . . . . . . . . . . . .  16
     5.2.  "redirect" Type . . . . . . . . . . . . . . . . . . . . .  17
     5.3.  "qrcode" Type . . . . . . . . . . . . . . . . . . . . . .  17
   6.  AS Response JSON  . . . . . . . . . . . . . . . . . . . . . .  17
     6.1.  Top Level Attributes  . . . . . . . . . . . . . . . . . .  18
     6.2.  "authorizations" Object . . . . . . . . . . . . . . . . .  18
     6.3.  "claims" Object . . . . . . . . . . . . . . . . . . . . .  19
     6.4.  Access Methods  . . . . . . . . . . . . . . . . . . . . .  20
Show full document text