IETF Logo Mail Archive

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

Fabien Imbault <fabien.imbault@gmail.com> Thu, 13 August 2020 15:18 UTC

Return-Path: <fabien.imbault@gmail.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 152E43A0D47 for <txauth@ietfa.amsl.com>; Thu, 13 Aug 2020 08:18:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 PaOJd7XW0ZuW for <txauth@ietfa.amsl.com>; Thu, 13 Aug 2020 08:18:02 -0700 (PDT)
Received: from mail-io1-xd31.google.com (mail-io1-xd31.google.com [IPv6:2607:f8b0:4864:20::d31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 885F73A0D4A for <txauth@ietf.org>; Thu, 13 Aug 2020 08:18:02 -0700 (PDT)
Received: by mail-io1-xd31.google.com with SMTP id u126so7577863iod.12 for <txauth@ietf.org>; Thu, 13 Aug 2020 08:18:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2m45iFZWfBBb60NUHuTSes9bEOG6qD90s/gv4JpU4dA=; b=b08Uc89Zvw+BrLT8L4Z1uNvyvJY9jXBdGUepS9q5alQujRoYkjzYhUBQl9AeROwFrW vqjMe2MOMiZXiKKDYWifZ7SBAX4FZQmKX9r8MhS5ZJ5lQ8rfIhtKgenx8fKdgoLJDbq+ Bvx34nr1NFxY3jvNjgc91EWY53T3ErRTK63y1HWa88DMXbe91ATvMBw8zOmtP0ZGW2fF 86MojDMLLuCXcDtuPpFxZX7OniwEYo32sYTFbUlGQ55+ZarAr+epbTZeympft9dRxojg ckfZGcuJX0knP5WNk05T3UmDUvJgj2sZkuOMlVprAYIYK57J6bPe9klIfxnjuaQC96+w NQKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2m45iFZWfBBb60NUHuTSes9bEOG6qD90s/gv4JpU4dA=; b=errFjRbtggleZs6F/woBQF+x5WHj5FS2CRqCeRKJ5pI+R6XYo8eFO7TqC90NOPgaZ4 LCZ+Y2eyoug9Av/fN5XoSwibh21Q4+44diMhuLiZiYdGRzseTztubCF+OSrdT7z7O4IR c3v/jLZF5ZdOefx3wKXeXcDqg5Ajt0yptniqDdI8w2ulz2Dm9fFM1vOaKs2UJE3x3Fn0 j5iqHmAiYBWgkg2hmzxcbKL8JqMPZwkEG2Pz6oqlp9WYardW4A78XcolH3F5cfj8ek2s VZt9Vd4MoXigQAf6B61Sps2G5Wt5VXMbRT4mkiB38bofDBwSPV3Ft5yL1GdKGgows6m/ QoWA==
X-Gm-Message-State: AOAM530de7rzXrP7zakRrnJXXnE38vtClyxgQFBVyajLQCcD/BXq1xiU CK2uDFvxI6WQ5S+mZwQIQupwo983MZkKLQXOyo8=
X-Google-Smtp-Source: ABdhPJzCvDr9wny34TFs7UugIKmKrbkv6wJbHo0QxpY5ILB8bExIDhViHl1buOUplb6n5GCNmS2iPW3GAQXIq8nMbFE=
X-Received: by 2002:a5d:841a:: with SMTP id i26mr5238589ion.144.1597331881723; Thu, 13 Aug 2020 08:18:01 -0700 (PDT)
MIME-Version: 1.0
References: <c5f40413-93b8-2e8c-0a3e-14a07cd27ad0@free.fr> <ECF217AE-1D67-4EAE-AE51-531F6EE6E222@mit.edu> <583aedda-ae41-1f3e-6623-671f2197614c@free.fr> <20200804185313.GT92412@kduck.mit.edu> <CAJot-L2hykst2vFxcwLn_auDMMaw7psVwsKFHKhQp9DA49ydWg@mail.gmail.com> <A4DC7B4E-FD34-454F-9396-B971CF5D57A4@mit.edu> <CAD9ie-tKEp+PV3F4p84Zbu7Kd1dQutawnzHybt8cmg-XniLYLQ@mail.gmail.com> <CAOW4vyN4ifCXmk1XAyGK4cEfY1jTp6+AWOL-uNjEpVcp0Ku0UQ@mail.gmail.com> <CAD9ie-ugjNevqKAPWFjKqGMMpCvX6yyC=M4bs9naenJf-k9uqg@mail.gmail.com> <CAOW4vyOrXstAvc3eKbsUh+gOPT-79nevR8nT5FyKTe+aAQ1pSw@mail.gmail.com> <CAD9ie-sZbxBKuLgC3Bu+yzJATOETdto=S83B6FOmC3gFJWz1jw@mail.gmail.com> <1b4a6a43-4c57-92b4-f442-2da58a2d0d70@free.fr> <CAD9ie-s5_tOZhE57tj1b+XaqDw+D43n_wStOPSmi7cioG2Z+gw@mail.gmail.com> <6678f154-31e7-2d01-2002-f3600f589c96@free.fr> <CD0AE256-7868-4B00-9235-300CB55506BC@mit.edu>
In-Reply-To: <CD0AE256-7868-4B00-9235-300CB55506BC@mit.edu>
From: Fabien Imbault <fabien.imbault@gmail.com>
Date: Thu, 13 Aug 2020 17:17:49 +0200
Message-ID: <CAM8feuS0K3OTmNY6fzYKOtZeh1_6r_+UhW3uBzT96agw56akRA@mail.gmail.com>
To: Justin Richer <jricher@mit.edu>
Cc: Denis <denis.ietf@free.fr>, "txauth@ietf.org" <txauth@ietf.org>, Francis Pouatcha <fpo@adorsys.de>, Benjamin Kaduk <kaduk@mit.edu>, Dick Hardt <dick.hardt@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000660c0d05acc3cf44"
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/y2jxSNdVbz2mYeQW4o1wdlYWexw>
Subject: Re: [GNAP] [Txauth] Revisiting the photo sharing example (a driving use case for the creation of OAuth)
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: Thu, 13 Aug 2020 15:18:05 -0000

Without surprise, +1 to differentiate between the back-channel and the
front-channel.

On Thu, Aug 13, 2020 at 5:15 PM Justin Richer <jricher@mit.edu> wrote:

> Denis, I want to focus on one point here:
>
> In OAuth 2.0, the user consent is performed by the AS using an authorize
> endpoint where the user consent is solicited and captured.
>
> Since a user, with no prior experience, shall first connect to a RS to
> perform an operation, the user consent shall be performed by the RS,
> instead of the AS. This means that we should define a "consent" endpoint
> at the RS.
>
>
> One of my goals with XYZ’s design was to be able to separate the
> interaction with the user from the web-based flows for the delegation
> protocol, and that aspect is enshrined in the GNAP charter as well.
>
> It points to the reality that there are two different aspects of the
> traditional AS that we might need to talk about separately now. One deals
> with delegation, issuing tokens, returning data directly to the client (not
> through a separate API, since that’s the RS), and other back-channel stuff.
> The other aspect deals with interacting with the user and/or resource
> owner.
>
> We already saw bits of this in OAuth 2: the AS is defined by the pair of
> the token endpoint and authorization endpoint, each filling the respective
> roles above. What if we formally separate these? Strawman names:
>
>
> Delegation Server (DS) - handles the back-channel stuff
>
> Interaction Server (IS) - handles the front-channel stuff
>
>
>  — Justin
>
> --
> TXAuth mailing list
> TXAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/txauth
>

v2.23.0 | Report a Bug | By Email