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

Dick Hardt <> Mon, 03 August 2020 17:15 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 31DB63A0F78 for <>; Mon, 3 Aug 2020 10:15:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 6_tCoI8C4W7k for <>; Mon, 3 Aug 2020 10:15:31 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8F7063A0F72 for <>; Mon, 3 Aug 2020 10:15:30 -0700 (PDT)
Received: by with SMTP id v4so30814780ljd.0 for <>; Mon, 03 Aug 2020 10:15:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dSC+qqDJU6zC+zzSieAlQNgphTQzmAAlyy0pzUuTY7I=; b=pxagjz8XVD/iw/VgYpDm9NY8UM3cwnD0hhOwwJP0paVS9ICBNHElGimrOJFK5t2AaP eQuph3LIC6TU77Ug3ecQLSSc6dluKfAzpc6Pi1zxA409TjZaYntsphtmZ+RH8BGGZ3Jd i8tNJlbdkc3wj2kPUSdA4kpUg+uROko7KrXSSeYofXhk0D09Ew39BYdZE17AqvjTHxXw fNzEyUIi7mpVsYevfbeY3qjz6WuCF7R2sIGP7R1tyhye0CcjAb77RppjwLeM8G6epIlK BeLBw6UMSfbUDKWTyk+hfHDrWv+4zMGhrC7pu/tHLyaGwH/xxrOunrylEVy2Q4Z/w80P vVGw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=dSC+qqDJU6zC+zzSieAlQNgphTQzmAAlyy0pzUuTY7I=; b=rX/6fa5s13zAzVGjUlGBAK4MYDSv1HFUCuPnDWNykGrfzEDfhfdlGrrp4Gj/hThOuR MhvDrRbSHxbAFopGKyCi4MM98TAPwA/VF2iD1PB9NjFufNCcXd6Ils236qqXJGGqwllB RXIgnJzVuk1IK0+XMcXKcZcUVHHnYZBSmQGBdOshNtGc5CLEGuA1+6mGc5Cuh5HGILJu YeiyNXPPPmZ0XIQYzR8IZ/viUTs1LI18kA7Dt/KFsnUY2HTCTvHIaIK9m92dle2AYfhd 34SCJghULBBSfH6tQo6UMLnuw6Ydmkyvpz7CWkV7JwVTKF+/qNCPe5XOh1uE2uuI1tgf MQcQ==
X-Gm-Message-State: AOAM530ZBcb0fdR6sLV6fPhklicm9XDdetQF7Sz4L9S7deBhv31q4qeW E3JeV61uVOhEVsdoFSmG3RG24pm3P1WT5468nGbvPyfu
X-Google-Smtp-Source: ABdhPJza3mC6yUuKdtvW/+cLQU3q4ZlUn4VR07uApIh8asT/SUj+pFISJoaf9eKx4u+rBmWBP2TXFPWxRDW0HH5jDEk=
X-Received: by 2002:a2e:9695:: with SMTP id q21mr7594633lji.437.1596474928409; Mon, 03 Aug 2020 10:15:28 -0700 (PDT)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Dick Hardt <>
Date: Mon, 3 Aug 2020 10:14:52 -0700
Message-ID: <>
To: Denis <>
Cc: "" <>
Content-Type: multipart/alternative; boundary="0000000000000032c805abfc49be"
Archived-At: <>
Subject: Re: [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: Mon, 03 Aug 2020 17:15:33 -0000

Hi Denis

In your proposed flow, how does RS2 know who the user is that it is dealing
with? In OAuth, the AS authenticates the User for the RS. In the photo
sharing example, the AS and RS are from the same organization, so the AS
knowing what the RS was doing was not an issue.

What you call a Client is not an OAuth Client, but is more of an agent for
the User. Microsoft InfoCards comes to mind as a comparable architecture,
and it seems aligned with what Tom is asking for.

On Mon, Aug 3, 2020 at 12:35 AM Denis <> wrote:

> Hello Dick,
> This is a follow-up of the thread: "Reviewing
> draft-hardt-xauth-protocol-11".
> Hereafter are three exchanges between you and me which triggered this new
> thread:
> [Dick]    The photo sharing example was a driving use case for the
> creation of OAuth.
> [Denis]  We would need to revisit the original scenario and consider if it
> can be addressed in a different way than the original way.
> [Dick]   The use case is the same. Is there a different solution you are
> proposing ?
> My response is : Yes indeed, I have a different solution to address the
> same use case.
> RFC 6749 and draft-ietf-oauth-v2-1-00 both state:
> For example, an end-user (resource owner) can grant a printing service
> (client) access to her protected photos stored at
> a photo-sharing service (resource server), without sharing her username
> and password with the printing service. Instead,
> she authenticates directly with a server trusted by the photo-sharing
> service (authorization server), which issues the printing
> service delegation-specific credentials (access token).
> There are no further explanations.
> Which information will be disclosed by the resource owner to the
> authorization server to get "the printing service delegation-specific
> credentials"
> is not described. It is a private agreement between the AS and the RS. It
> is more than likely that the authorization server will learn information
> about which operation the resource owner is wishing to perform and where.
> Since in OAuth, the access token is supposed to be opaque to the Client,
> the user will be unable to make sure that her instructions have been
> carefully followed.
> RFC 6749 and draft-ietf-oauth-v2-1-00 both share a common point: they do
> not contain a "Privacy Considerations" section.
> Thus, the leakage of information to the AS is not discussed.
> It is possible to revisit the original scenario by applying "Privacy by
> design" principles.
> The scenario can be solved by using an old data transfer method that has
> been first described 32 years ago under the name
> "Referenced Data Transfer (RDT)" in ECMA-131 (1988) and a few years later
> in ISO/IEC 10740-2:1993.
> RDT allows two servers to directly exchange large amounts of data under
> the supervision of a client by communicating, through the client,
> a reference generated by one server to the other server. RDT does not use
> any Authorization Server (AS). This means that no AS is able
> to act as Big Brother and this solves a major privacy concern.
> * The three entities involved *
> The Client supporting a User (was the Resource Owner).
> The Photo-sharing service (was the Resource Server) : RS1.
> The Printing service (was the client): RS2.
> *Flow of operations with the Photo-sharing service (RS1) *The Client
> first connects to the photo-sharing service (RS1) and the User
> authenticates to the photo-sharing service (RS1).
> RS1 to User: "Please select the operation to be performed".
> Operation selected: "Print pictures using a third party printing service".
> RS1 to User: "Please select a set of pictures to be printed".
> The User selects the pictures.
> RS 1 User consent: "Do you agree RS1 to communicate your selection of
> pictures to a third party printing service" ?
> If the User consents, RS1 to Client: "Here is the reference to be used by
> your printing service to get the selected pictures".
> * Flow of operations with the Printing service* (
> *RS2) *
> The Client connects to the printing service (RS2) and the User
> authenticates to the printing service (RS2).
>             *Note*: This allows to make sure that the user has an account
> on RS2 so that further operations can be charged to this account
>                       and that the prints can be sent to a known address.
> RS2 to User: "Please select the operation to be performed".
> Operation : "Print pictures to be received from a photo-sharing service ".
> RS2 to User: "Please indicate your photo-sharing service".
> The User responds: RS1.
> "Please enter the reference to be used by RS2 to receive the set of
> pictures from RS1".
> The Client (or the User) enters the reference generated by RS1.
> RS2 contacts RS1 using that reference in order to get the characteristics
> and the thumbnails of the pictures to be printed (i.e. not yet the whole
> pictures).
> RS2 to client: What are your printing preferences for each picture (e.g.
> number of prints, size, quality of the paper, resolution, margins, colours,
> etc... ) ?
> The User responds to all these questions.
> RS 2 User consent: This operation will be charged XX € ? Do you agree ?
> If the payment needs to be done on-line, then a payment phase is inserted.
> * Continuation of the flow of operations *Final message from RS1 to the
> Client: "Your selection of pictures will be soon transmitted to RS2".
> Final message from RS2 to the Client: "Your prints will be soon on their
> way".
> RS2 to RS1 (asynchronous): transmit the set of pictures corresponding to
> this reference.
> * Some of the advantages of RDT*
>    1. An end-user can grant a printing service (RS2) access to her
>    protected photos stored at a photo-sharing service (RS1),
>    without sharing her username and password with the printing service.
>    2. Neither RS1, nor RS2 need to use or to trust any AS. This solves
>    the Big Brother privacy issue.
>    3. Any authentication method supported by RS1 or RS2 can be used by
>    the User.
>    4. The User can use any photo-sharing service (RS1) with any printing
>    service (RS2), as long as they both support RDT.
>    5. The User consent is first performed with the photo-sharing service
>    (RS1) and then after with the printing service (RS2).
>    6. The reference generated by RS1 will only be accepted by RS1 during
>    a time period.
>    7. The reference generated by RS1 allows RS2 to query first the
>    thumbnails and then after the pictures selected by the User at RS1.
>    8. The data transfer of the pictures selected at RS1 by the User is
>    performed asynchronously from RS1 to RS2 as a back-office operation.
> *Questions*: What would be the full scenario of this use case using OAuth
> ? What about Privacy Considerations ?
> Denis