Re: [GNAP] [Txauth] Revisiting the photo sharing example (a driving use case for the creation of OAuth)

Justin Richer <> Fri, 14 August 2020 14:28 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 53CD73A0C7C for <>; Fri, 14 Aug 2020 07:28:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id mKJaV_t64LbZ for <>; Fri, 14 Aug 2020 07:28:30 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 29C833A0C5E for <>; Fri, 14 Aug 2020 07:28:29 -0700 (PDT)
Received: from [] ( []) (authenticated bits=0) (User authenticated as jricher@ATHENA.MIT.EDU) by (8.14.7/8.12.4) with ESMTP id 07EESLSA002254 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 14 Aug 2020 10:28:22 -0400
From: Justin Richer <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_54F77929-EE5C-40DA-8430-654209820622"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
Date: Fri, 14 Aug 2020 10:28:21 -0400
In-Reply-To: <>
Cc: Dave Tonge <>, Dick Hardt <>, Francis Pouatcha <>, Denis <>, "" <>, Benjamin Kaduk <>
To: Fabien Imbault <>
References: <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <>
X-Mailer: Apple Mail (2.3608.
Archived-At: <>
Subject: Re: [GNAP] [Txauth] Revisiting the photo sharing example (a driving use case for the creation of OAuth)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 14 Aug 2020 14:28:32 -0000

I think the roles are linked, but so are the roles of the AS and RS (since the RS needs to trust and understand what the AS issues, ultimately). But by talking about them as separate roles, we can talk about ways to connect them, much the way that separating the AS from the RS (which were both just the “server” in OAuth 1) let us talk about JWTs and token introspection as methods for connecting the two.

And the thing is, people are already deploying the token-issuing portions and the interactive portions separately. For example these all point towards that: <> <> <>

Additionally, this is similar to how Google deploys OAuth 2 today, with the user interactive portion and the token-issuing portion in separate trust domains. We can label these parts separately without defining a single method of connecting them, and importantly without assuming they’ll be in the same box for someone’s deployment. 

 — Justin

> On Aug 14, 2020, at 2:29 AM, Fabien Imbault <> wrote:
> Thanks, that's an important use case. Should add DID also. 
> This raises additional questions related to claim aggregation though, in case you have contradictory information.
> Le ven. 14 août 2020 à 03:39, Dave Tonge < <>> a écrit :
> > I agree with clearly separating the GS interaction with the Client from the interaction with the User. 
> > I'm having a hard time viewing those as two different roles. They are two different interactions. Just as the client interaction with the AS is different from the client interaction with the GS.
> I also struggle to see these as different roles - they seem to be fundamentally linked, 
> However what I think does need to be taken into consideration is that there may be multiple Grant Servers involved in a user flow (I've added a new use case to describe some of these flows: <>)
> Moneyhub Enterprise is a trading style of Moneyhub Financial Technology Limited which is authorised and regulated by the Financial Conduct Authority ("FCA"). Moneyhub Financial Technology is entered on the Financial Services Register (FRN 809360) at <>. Moneyhub Financial Technology is registered in England & Wales, company registration number 06909772. Moneyhub Financial Technology Limited 2020 © Moneyhub Enterprise, Regus Building, Temple Quay, 1 Friary, Bristol, BS1 6EA. 
> DISCLAIMER: This email (including any attachments) is subject to copyright, and the information in it is confidential. Use of this email or of any information in it other than by the addressee is unauthorised and unlawful. Whilst reasonable efforts are made to ensure that any attachments are virus-free, it is the recipient's sole responsibility to scan all attachments for viruses. All calls and emails to and from this company may be monitored and recorded for legitimate purposes relating to this company's business. Any opinions expressed in this email (or in any attachments) are those of the author and do not necessarily represent the opinions of Moneyhub Financial Technology Limited or of any other group company.