Re: [GNAP] draft-hardt-xauth-protocol-14 update - reworked introduction

Mark Lizar <mark@openconsent.com> Sun, 16 August 2020 23:59 UTC

Return-Path: <mark@openconsent.com>
X-Original-To: txauth@ietfa.amsl.com
Delivered-To: txauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 934633A1213 for <txauth@ietfa.amsl.com>; Sun, 16 Aug 2020 16:59:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=openconsent.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J4e4-XV52QtK for <txauth@ietfa.amsl.com>; Sun, 16 Aug 2020 16:59:03 -0700 (PDT)
Received: from NAM10-BN7-obe.outbound.protection.outlook.com (mail-bn7nam10on2121.outbound.protection.outlook.com [40.107.92.121]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8DC83A0B55 for <txauth@ietf.org>; Sun, 16 Aug 2020 16:59:02 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=GZ9O/Fm0r8XcfJJLZmu2LsuFBnviex65f4BIHb/Ym0zxJrMm/cMr9pYAR28n/rWVV7AHqjXwomwGZIzqxb7AmwC3BGwqY1vmkQIOYxypAyS7PzluDzZRqRyei46e6yOvP1VvkJl74cPg8+QMnO/zsP3iO710YvkPMDmXN9fohkFwKJEOP3bViAkYEb39sx3Ud0D45NMksIdy+YRw7VfRIJaEPyKscyaTcHykRo381Elw242MxAokGXLiwASuztKKahmcQsjylXHZijeAFzCQe6ZJL5/be4SqsH/IhWoh9P8WskN2Yibvnle3XnO64ONjf1D8XlxJBsQWlCfUTF7stQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=0AKtZT9SxkexIo+ECvvki0xyBjCxeGzpHr77/m8it88=; b=M2bcDFDA2sYEuds/JPVdlp2kOaMSvRJhxkv5eB6QomVTsD3CofbuFUufqpx42Mrkp1C3FLNuQ0fSRatBl0Qq4VJRlxfkjASnFBHSCug5HVZ32zgCawv9RBdUkFaistCArq6ICTEDm+xw6oKmv9qXGymYS2obtM5+ehr9nVXA6l58Uyntz1K60j+NtdMIARYLy9CmcWpyXXtLwkZRrafFik0x+0L9Wn56H+t53wspKbRiRAyLgEx///iuIrvN6d4Dz/MDlN490lthU/40nbVDFNrAKL36p8FgVE7CkNWk+Zjlrjxl2oEaebqRcn6jXmtq3S1CZwwWiBoiEVfkYHzrkA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=openconsent.com; dmarc=pass action=none header.from=openconsent.com; dkim=pass header.d=openconsent.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=openconsent.onmicrosoft.com; s=selector1-openconsent-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=0AKtZT9SxkexIo+ECvvki0xyBjCxeGzpHr77/m8it88=; b=girW21PghZ8wrvsbJ38FV4NN2SX77XsePnYN62skjSDKrqQcUnLKxDxVUYDN6IGnbzf2CsryGeaEbljO3rFnbhh8Gyn9LhaQmVo6wF6gVF+HQl4mJn/6cDz+124OYrka4kkOhoybEJSGzdOXYDS6vHkCjwAevfwpfS3ZeeFgqXHnRXcXVgX5MiXlTFetnwusy+bXOkSsTeDzwfUGyuclToPLBPq3SgkG6zVVBprE6Gqnkx3fsVp3ihbdUHLPXjkSYX8jeXEERgx7jjuwuclARxg1dZ2csSheRqxMDbdj6mLEW/nFgfLgiUGS7Mf5aBkutfIo5tOEKPOBVHjhq14Isg==
Received: from CY4PR14MB1752.namprd14.prod.outlook.com (2603:10b6:903:15b::16) by CY4PR1401MB2039.namprd14.prod.outlook.com (2603:10b6:910:24::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3283.15; Sun, 16 Aug 2020 23:58:55 +0000
Received: from CY4PR14MB1752.namprd14.prod.outlook.com ([fe80::48ec:df78:c9cf:5b25]) by CY4PR14MB1752.namprd14.prod.outlook.com ([fe80::48ec:df78:c9cf:5b25%3]) with mapi id 15.20.3283.027; Sun, 16 Aug 2020 23:58:55 +0000
From: Mark Lizar <mark@openconsent.com>
To: Tom Jones <thomasclinganjones@gmail.com>, Francis Pouatcha <fpo=40adorsys.de@dmarc.ietf.org>
CC: GNAP Mailing List <txauth@ietf.org>, Dick Hardt <dick.hardt@gmail.com>
Thread-Topic: [GNAP] draft-hardt-xauth-protocol-14 update - reworked introduction
Thread-Index: AQHWdB8pD0Ff2eMBkkiD+DL+ZQG9f6k7ZF6AgAAEkh4=
Date: Sun, 16 Aug 2020 23:58:55 +0000
Message-ID: <CY4PR14MB1752A444DB20E509F1B74357DA5E0@CY4PR14MB1752.namprd14.prod.outlook.com>
References: <CAD9ie-v_1GHHJWVeXb5cXiUELj-Un7BN6uCdqSRz4qjL_rq=UQ@mail.gmail.com> <CAOW4vyPEzcC0HCM2eRvZ3yjRp_S4rFdVcqqH3gmnpfbCLx-KNg@mail.gmail.com>, <CAK2Cwb47h=yHpbabY8xERArN6589q+cEaPU583iNW7ksc8_r4A@mail.gmail.com>
In-Reply-To: <CAK2Cwb47h=yHpbabY8xERArN6589q+cEaPU583iNW7ksc8_r4A@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=openconsent.com;
x-originating-ip: [162.253.71.20]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b674cee1-1816-4641-53f3-08d8424055a4
x-ms-traffictypediagnostic: CY4PR1401MB2039:
x-microsoft-antispam-prvs: <CY4PR1401MB20390396127E0F8CB4E0E211DA5E0@CY4PR1401MB2039.namprd14.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6790;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: i7yKYkRoORDgJmHEM4R9jH7qy1VffeuFoehOmFjtWrn+FFyzYOlfZqxv1/qsKYP1JHE3fjeCGB6OHwe1jBHPWGFh99sxFn6hq5WlkPvRIJ/9+NqbsI6zQ6fBKl/oAVi00pk83Rfd4BoEkVy3V55GLwiPpOmy5ZBUsNsqpvshu4g2MqkZOTb7GODPoc4R527x4x7gdFFmXdoaQ7tVblGMTGLtVzJewHVv/58OSfoQl0VQwUp0BQ86K/kEldmC0RHDqRVEeT5KhvaNXqBZo+EBQEjoB8YwhY3dnvU0RWIOySQVwNWrG1tMh/ItCg+rMfA2ByjzwE2xyprkognTomg/mn2OZ4YhQI7IVFObGNYucSYZSmP4xvaGymklBcwqVBvt4g0bo6IBXbEb5YwmTb8AuA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:CY4PR14MB1752.namprd14.prod.outlook.com; PTR:; CAT:NONE; SFS:(34096005)(136003)(366004)(396003)(346002)(39830400003)(376002)(966005)(55016002)(76116006)(66574015)(26005)(83380400001)(316002)(66446008)(66556008)(2906002)(66946007)(186003)(9686003)(71200400001)(64756008)(21615005)(66476007)(30864003)(15650500001)(478600001)(83080400001)(110136005)(4326008)(33656002)(8676002)(8936002)(7696005)(54906003)(86362001)(166002)(52536014)(53546011)(6506007)(45080400002)(5660300002)(579004)(559001); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: mc1/Wi1Si4XAxTZC/psyp6WA2lQEYrjL3hUyewdRjPA3rQ2sMFqWuSg+14TXpp1VVuD8JCCyufsUGNe2/txIU/muZI/Ce3MeTnGuTPis4dZX2VFVuQNV/3B3yUL/IFuJYI1RiqkQYCsIh7CRqQb6oRM46TMda348Z9h1owOThsqIiVDQu8Nour1v5az1Wvfvng+Lsyz+yyqbxnQjn0JPGeswEgqkVGQr83L0PjJc3S0Y05MPF4BLsMbJP9eqRO03IGfOKpSpSBvadp8ebFQuoFiCpeE31mNR77pHwvb+ABJGG6fLhpARYTKjr/Zj+8KOU8JCsGFHzAotMf0UKkTgxwCob9B78KPtIyFwerZPA/Kk6rffN1R1zPoysyLaHYKyzt2OdIFnp58n70lAllYcGIorZXapFMnnHBoD4pdrNrEMFlDo9cGnV5Cp6ng8Gm8Fc57Iggo9tm+lP8m/ns1c2RKbtRoiRAW67xRrWf6c4VyC+xMv1RPFZ79KVBTHWBCYMbJlgWkSFyDsg/UgjAfh6sAn+xjUeX0MfwGLaTWHhWsFzifP1oaOBbgivliN9uZTqGeePiZuWbIIkrYXZCXEdyGZzf3nCe5dw4cEgYA2dAgT+7YASibuJEzsqwU0OvLGPjlZXriiNWnG1kiYmv28fQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CY4PR14MB1752A444DB20E509F1B74357DA5E0CY4PR14MB1752namp_"
MIME-Version: 1.0
X-OriginatorOrg: openconsent.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CY4PR14MB1752.namprd14.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: b674cee1-1816-4641-53f3-08d8424055a4
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Aug 2020 23:58:55.4058 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: d6e4f995-32e4-4f49-9949-0abe865e4152
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: jlMBu1nyqXjXo6h8ZBQ7mFi3KeTWdX/Hr2h+k7lHmea3jTxlY/Ub4MuA2YZgLs8fXYA3x6nVCKNFAMb6DUQyIg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR1401MB2039
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/toLo73CMjzwasgCns9LGk_rrEEk>
Subject: Re: [GNAP] draft-hardt-xauth-protocol-14 update - reworked introduction
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <txauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/txauth>, <mailto:txauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/txauth/>
List-Post: <mailto:txauth@ietf.org>
List-Help: <mailto:txauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/txauth>, <mailto:txauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Aug 2020 23:59:08 -0000

- consent is the human management of a permission grant the system manages .   +1 for not mixing human and system terms for the same endpoint.

Get Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: TXAuth <txauth-bounces@ietf.org> on behalf of Tom Jones <thomasclinganjones@gmail.com>
Sent: Sunday, August 16, 2020 7:38:13 PM
To: Francis Pouatcha <fpo=40adorsys.de@dmarc.ietf.org>
Cc: GNAP Mailing List <txauth@ietf.org>rg>; Dick Hardt <dick.hardt@gmail.com>
Subject: Re: [GNAP] draft-hardt-xauth-protocol-14 update - reworked introduction

i disagree - end user needs to be a human = use term like subject or endpoint if you want a non-human
Peace ..tom


On Sun, Aug 16, 2020 at 3:46 PM Francis Pouatcha <fpo=40adorsys.de@dmarc.ietf.org<mailto:40adorsys.de@dmarc.ietf.org>> wrote:
Hello Dick, my feedback below:

1.2: Excellent and Focussed
-> The word "Grant Client" looks great for me.

1.3:
Title: Human Interaction -> End User Interaction
I would title this "End User" interaction and not "human ....". It is not about having a human, but a terminating edge of the protocol. An "End User" can be either human on an IOT device or a car or ...

Participant: User -> "Requesting Party"
I will still insist on replacing the word "User" with a role name. Maybe "Requesting Party" as used by UMA.

Participant: "Resource Controller". In past discussions there was a consensus on using "Resource Controller" instead.

(B) I which the GS never interacts with the "Requesting Party" in a matter of obtaining a grant to a resource (many reasons: privacy, confidentiality, abstraction, ...). Generally the GS will need information (claims) about the "Requesting Party" to proceed with the authorisation decision. In this case, the GS can instruct the GC to obtain those claims. In some cases, claims on the "Requesting Party" will be obtained from another "Authorization Server" (AS). The word AS is intentionally chosen here. In this same login, the path (C0, C1) below will not only return the RC consent, but might also return some claims on RC.

ASs provide authentication "of" and consent collection "from" End Users. End users are in this case the Requesting Party, and the Resource Controller).

The result can look like the modified diagram below. With this we can address some privacy concerns that are being discussed on the list.

    +-------------+                        +----------------+
    | Requesting  |                        |  Resource      |
    | Party (RP)  |                        | Controller (RC)|
    +-------------+                        +----------------+
        +     +                             +
        +      +                           +
       (A)     (B1)                      (C1)
        +        +                       +
        +.        +                     +
        +       +--------+       +--------+
        +       | RP-AS  |       | RC-AS  |
        +       |        |       |        |
        +       +--------+       +--------+
        +         +                  +
        +       (B0)                +
        +       +                (C0)
    +--------+ +                  +          +------------+
    | Grant  | - - - -(1)- - - - + - - - - ->|  Resource  |
    | Client |                  +            |   Server   |
    |  (GC)  |       +---------------+       |    (RS)    |
    |        |--(2)->|     Grant     |       |            |
    |        |<-(3)->|     Server    |- (6) -|            |
    |        |<-(4)--|      (GS)     |       |            |
    |        |       +---------------+       |            |
    |        |                               |            |
    |        |--------------(5)------------->|            |
    +--------+                               +------------+

(B0, B1) replace (B). Occur inside step (3), GS asks GC to collect the claims. GC contacts RP-AS to negotiate those claims. But it is important to mention that those Claims-RP are not the target Grant being negotiated for the resource access. They are generally used by GS (and later RS) as input into performing authz decisions.

(C0, C1) replace (C). They occur after step (3) (Beware of the difference to Bs that occur inside 3). This separation address the Big Brother problem we have been discussing in the list.

Essential is to mention that in an instantiation of this model for oAuth for example:
- GS, RP-AS and RC-AS might be the same entity.
- RP and RC might refer to the same "End User".

Off-topic: The splitting of GS and AS was suggested in some discussions on the mailing list. But we have no mean yet to isolate good inputs for later reuse. This is why I suggest we compile some inputs into tickets or wiki pages (like use cases).

1.4:
The Trust model introduces what I would rather call the trust framework. The purpose of the trust framework will be to address topics mentioned in this section. There is still a lot of discussion needed to have a structure for this section.


1.5
I suggest again we replace Human with "End User" and still make them roles. This is:
Terminology (Are all roles)
  -> These roles can be borne by End Users
     -> Requesting Party (RP)
     -> Resource Controller (RC)
  -> These role can be borne by Services
     -> GS
     -> GC
     -> RS
     -> RP-AS
     -> RC-AS

I will stop here, as the fundamental agreement on this structure is necessary for a qualified review of section 2++.

Best regards
/Francis

On Sat, Aug 15, 2020 at 7:03 PM Dick Hardt <dick.hardt@gmail.com<mailto:dick.hardt@gmail.com>> wrote:
Hello

I just pushed an updated version of XAuth:

https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html

Highlights:

  *   renamed Client -> Grant Client
  *   Introduced Client Owner, Grant Server Owner as new entities
  *   renamed Authorizations -> Access
  *   An Access contains an array of RAR objects now
  *   Reworked diagram an intro to focus on Grant, and separate protocol roles from human interactions.

New introduction included below for your convenience

/Dick

  *

1. <https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1> Introduction<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#name-introduction>

EDITOR NOTE<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1-1>

This document captures a number of concepts that may be adopted by the proposed GNAP working group. Please refer to this document as:<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1-2>

XAuth<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1-3>

The use of GNAP in this document is not intended to be a declaration of it being endorsed by the GNAP working group.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1-4>

This document describes the core Grant Negotiation and Authorization Protocol (GNAP). The protocol supports the widely deployed use cases supported by OAuth 2.0 [RFC6749<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#RFC6749>] & [RFC6750<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#RFC6750>]0>], OpenID Connect [OIDC<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#OIDC>] - an extension of OAuth 2.0, as well as other extensions. Related documents include: GNAP - Advanced Features [GNAP_Advanced<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#GNAP_Advanced>] and JOSE Authentication [JOSE_Authentication<https://tools.ietf..org/id/draft-hardt-xauth-protocol-14.html#JOSE_Authentication>] that describes the JOSE mechanisms for client authentication.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1-5>

The technology landscape has changed since OAuth 2.0 was initially drafted. More interactions happen on mobile devices than PCs. Modern browsers now directly support asymetric cryptographic functions. Standards have emerged for signing and encrypting tokens with rich payloads (JOSE) that are widely deployed.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1-6>

GNAP simplifies the overall architectural model, takes advantage of today's technology landscape, provides support for all the widely deployed use cases, offers numerous extension points, and addresses many of the security issues in OAuth 2.0 by passing parameters securely between parties rather than via a browser redirection.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1-7>

While GNAP is not backwards compatible with OAuth 2.0, it strives to minimize the migration effort.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1-8>

The suggested pronunciation of GNAP is "guh-nap".<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1-9>

1.1. <https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.1> The Grant<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#name-the-grant>

The Grant is at the center of the protocol between a client and a server. A Grant Client requests a Grant from a Grant Server. The Grant Client and Grant Server negotiate the Grant. The Grant Server acquires authorization to grant the Grant to the Grant Client. The Grant Server then returns the Grant to the Grant Client.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.1-1>

The Grant Request may contain information about the User, the Grant Client, the interaction modes supported by the Grant Client, the requested identity claims, and the requested resource access. Extensions may define additional information to be included in the Grant Request.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.1-2>

1.2. <https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.2> Protocol Roles<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#name-protocol-roles>

There are three roles in GNAP: the Grant Client (GC), the Grant Server (GS), and the Resource Server (RS). Below is how the roles interact:<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.2-1>

    +--------+                               +------------+
    | Grant  | - - - - - - -(1)- - - - - - ->|  Resource  |
    | Client |                               |   Server   |
    |  (GC)  |       +---------------+       |    (RS)    |
    |        |--(2)->|     Grant     |       |            |
    |        |<-(3)->|     Server    |- (6) -|            |
    |        |<-(4)--|      (GS)     |       |            |
    |        |       +---------------+       |            |
    |        |                               |            |
    |        |--------------(5)------------->|            |
    +--------+                               +------------+


<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.2-2>

(1) The GC may query the RS to determine what the RS requires from a GS for resource access. This step is not in scope for this document.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.2-3>

(2) The GC makes a Grant request to the GS (Create Grant Section 3.2<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#CreateGrant>)t>). How the GC authenticates to the GS is not in scope for this document. One mechanism is [JOSE_Authentication<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#JOSE_Authentication>].<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.2-4>

(3) The GC and GS may negotiate the Grant.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.2-5>

(4) The GS returns a Grant to the GC (Grant Response Section 4.1<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#GrantResponse>).<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.2-6>

(5) The GC accesses resources at the RS (RS Access Section 6<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#RSAccess>).<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.2-7>

(6) The RS evaluates access granted by the GS to determine access granted to the GC. This step is not in scope for this document.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1..2-8>

1.3. <https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.3> Human Interactions<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#name-human-interactions>

The Grant Client may be interacting with a human end-user (User), and the Grant Client may need to get authorization to release the Grant from the User, or from the owner of the resources at the Resource Server, the Resource Owner (RO)<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.3-1>

Below is when the human interactions may occur in the protocol:<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.3-2>

    +--------+                               +------------+
    |  User  |                               |  Resource  |
    |        |                               | Owner (RO) |
    +--------+                               +------------+
        +     +                             +
        +      +                           +
       (A)     (B)                       (C)
        +        +                       +
        +         +                     +
    +--------+     +                   +     +------------+
    | Grant  | - - -+- - - -(1)- - - -+- - ->|  Resource  |
    | Client |       +               +       |   Server   |
    |  (GC)  |       +---------------+       |    (RS)    |
    |        |--(2)->|     Grant     |       |            |
    |        |<-(3)->|     Server    |- (6) -|            |
    |        |<-(4)--|      (GS)     |       |            |
    |        |       +---------------+       |            |
    |        |                               |            |
    |        |--------------(5)------------->|            |
    +--------+                               +------------+

Legend
+ + + indicates an interaction with a human
----- indicates an interaction between protocol roles


<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.3-3>

Steps (1) - (6) are the same as Section 1.2<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#ProtocolRoles>es>. The addition of the human interactions (A) - (C) are bolded below.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.3-4>

(A) The User is interacting with a GC, and the GC needs resource access and/or identity claims (a Grant)<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.3-5>

(1) The GC may query the RS to determine what the RS requires from a GS for resource access<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.3-6>

(2) The GC makes a Grant request to the GS<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.3-7>

(3) The GC and GS may negotiate the Grant<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.3-8>

(B) The GS may interact with the User for grant authorization<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.3-9>

(C) The GS may interact with the RO for grant authorization<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.3-10>

(4) The GS returns a Grant to the GC<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.3-11>

(5) The GC accesses resources at the RS<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.3-12>

(6) The RS evaluates access granted by the GS to determine access granted to the GC<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.3-13>

Alternatively, the Resource Owner could be a legal entity that has a software component that the Grant Server interacts with for Grant authorization. This interaction is not in scope of this document.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.3-14>

1.4.. <https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.4> Trust Model<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#name-trust-model>

In addition to the User and the Resource Owner, there are three other entities that are part of the trust model:<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.4-1>

  *   Client Owner (CO) - the legal entity that owns the Grant Client.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.4-2.1>
  *   Grant Server Owner (GSO) - the legal entity that owns the Grant Server.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.4-2.2>
  *   Claims Issuer (Issuer) - a legal entity that issues identity claims about the User. The Grant Server Owner may be an Issuer, and the Resource Owner may be an Issuer.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.4-2.3>

These three entities do not interact in the protocol, but are trusted by the User and the Resource Owner:<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.4-3>

  +------------+           +--------------+----------+
  |    User    | >> (A) >> | Grant Server |          |
  |            |           | Owner (GSO)  |          |
  +------------+         > +--------------+          |
        V              /          ^       |  Claims  |
       (B)          (C)          (E)      |  Issuer  |
        V          /              ^       | (Issuer) |
  +------------+ >         +--------------+          |
  |  Client    |           |   Resource   |          |
  | Owner (CO) | >> (D) >> |  Owner (RO)  |          |
  +------------+           +--------------+----------+


<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.4-4>

(A) User trusts the GSO to acquire authorization before making a grant to the CO<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.4-5>

(B) User trusts the CO to act in the User's best interest with the Grant the GSO grants to the CO<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.4-6>

(C) CO trusts claims issued by the GSO<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.4-7>

(D) CO trusts claims issued by the RO<https://tools.ietf..org/id/draft-hardt-xauth-protocol-14.html#section-1.4-8>

(E) RO trusts the GSO to manage access to the RO resources<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.4-9>

1.5. <https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1..5> Terminology<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#name-terminology>

Roles<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-1>

  *   Grant Client (GC)<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-2.1.1>

     *   may want access to resources at a Resource Server<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-2.1.2.1>
     *   may be interacting with a User and want identity claims about the User<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-2.1.2.2>
     *   requests the Grant Service to grant resource access and identity claims<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-2.1.2.3>
  *   Grant Server (GS)<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-2.2.1>

     *   accepts Grant requests from the GC for resource access and identity claims<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-2.2.2.1>
     *   negotiates the interaction mode with the GC if interaction is required with the User<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-2.2.2.2>
     *   acquires authorization from the User before granting identity claims to the GC<https://tools..ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-2.2.2.3>
     *   acquires authorization from the RO before granting resource access to the GC<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-2.2.2.4>
     *   grants resource access and identity claims to the GC<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-2.2.2.5>
  *   Resource Server (RS)<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-2.3.1>

     *   has resources that the GC may want to access<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-2.3.2.1>
     *   expresses what the GC must obtain from the GS for access through documentation or an API. This is not in scope for this document<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-2.3.2.2>
     *   verifies the GS granted access to the GC, when the GS makes resource access requests<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-2.3.2.3>

Humans<https://tools.ietf..org/id/draft-hardt-xauth-protocol-14.html#section-1.5-3>

  *   User<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-4.1.1>

     *   the person interacting with the Grant Client.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-4.1.2.1>
     *   has delegated access to identity claims about themselves to the Grant Server.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-4.1.2.2>
     *   may authenticate at the GS..<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-4.1.2.3>
  *   Resource Owner (RO)<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-4.2.1>

     *   the legal entity that owns resources at the Resource Server (RS).<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-4.2.2.1>
     *   has delegated resource access management to the GS.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-4.2.2..2>
     *   may be the User, or may be a different entity that the GS interacts with independently.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-4.2.2.3>

Reused Terms<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-5>

  *   access token - an access token as defined in [RFC6749<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#RFC6749>] Section 1.4.. An GC uses an access token for resource access at a RS.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1..5-6.1>
  *   Claim - a Claim as defined in [OIDC<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#OIDC>] Section 5. Claims are issued by a Claims Issuer.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-6.2>
  *   Client ID - a GS unique identifier for a Registered Client as defined in [RFC6749<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#RFC6749>] Section 2.2.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-6.3>
  *   ID Token - an ID Token as defined in [OIDC<https://tools.ietf..org/id/draft-hardt-xauth-protocol-14.html#OIDC>] Section 2. ID Tokens are issued by the GS. The GC uses an ID Token to authenticate the User.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-6.4>
  *   NumericDate - a NumericDate as defined in [RFC7519<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#RFC7519>] Section 2.<https://tools..ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-6.5>
  *   authN - short for authentication.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-6.6>
  *   authZ - short for authorization.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-6.7>

New Terms<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-7>

  *   GS URI - the endpoint at the GS the GC calls to create a Grant, and is the unique identifier for the GS.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-8.1>
  *   Registered Client - a GC that has registered with the GS and has a Client ID to identify itself, and can prove it possesses a key that is linked to the Client ID. The GS may have different policies for what different Registered Clients can request.. A Registered Client MAY be interacting with a User.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-8.2>
  *   Dynamic Client - a GC that has not been previously registered with the GS, and each instance will generate it's own asymetric key pair so it can prove it is the same instance of the GC on subsequent requests.. The GS MAY return a Dynamic Client a Client Handle for the Dynamic Client to identify itself in subsequent requests. A single-page application with no active server component is an example of a Dynamic Client.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-8.3>
  *   Client Handle - a unique identifier at the GS for a Dynamic Client for the Dynamic Client to refer to itself in subsequent requests.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-8.4>
  *   Interaction - how the GC directs the User to interact with the GS. This document defines the interaction modes: "redirect", "indirect", and "user_code" in Section 5<https://tools..ietf.org/id/draft-hardt-xauth-protocol-14.html#InteractionModes>.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-8.5>
  *   Grant - the user identity claims and/or resource access the GS has granted to the Client. The GS MAY invalidate a Grant at any time.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-8.6>
  *   Grant URI - the URI that represents the Grant. The Grant URI MUST start with the GS URI.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-8.7>
  *   Access - the access granted by the RO to the GC and contains an access token. The GS may invalidate an Access at any time.<https://tools.ietf.org/id/draft-hardt-xauth-protocol-14.html#section-1.5-8.8>
  *   Access URI - the URI that represents the Access the GC was granted by the RO. The Access URI MUST start with the GS URI.. The Access URI is used to refresh an access token.


--
TXAuth mailing list
TXAuth@ietf.org<mailto:TXAuth@ietf.org>
https://www.ietf.org/mailman/listinfo/txauth


--
Francis Pouatcha
Co-Founder and Technical Lead
adorsys GmbH & Co. KG
https://adorsys-platform.de/solutions/
--
TXAuth mailing list
TXAuth@ietf.org<mailto:TXAuth@ietf.org>
https://www.ietf.org/mailman/listinfo/txauth