Re: [OAUTH-WG] third party applications

Dima Postnikov <dima@postnikov.net> Wed, 02 September 2020 00:20 UTC

Return-Path: <dima.postnikov@gmail.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE3113A0821 for <oauth@ietfa.amsl.com>; Tue, 1 Sep 2020 17:20:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=postnikov-net.20150623.gappssmtp.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 MocX-0g_npDs for <oauth@ietfa.amsl.com>; Tue, 1 Sep 2020 17:20:10 -0700 (PDT)
Received: from mail-pf1-x433.google.com (mail-pf1-x433.google.com [IPv6:2607:f8b0:4864:20::433]) (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 DCCAE3A0853 for <oauth@ietf.org>; Tue, 1 Sep 2020 17:20:10 -0700 (PDT)
Received: by mail-pf1-x433.google.com with SMTP id d22so1822273pfn.5 for <oauth@ietf.org>; Tue, 01 Sep 2020 17:20:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=postnikov-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pJ/tVTtwyTx+gneArooEfMYy80zoBRfXnwFMAqumtoU=; b=F3L2crl87xhERSCyth54l6G+2kIC1lZDoq99/iQkhMC9r0hG1DiBL6/cjyXmJkjwCM y0/CxjY7UvNWFX8znZcP2VqnalkIr3XM2yIaw5Zs+FC3lP8D3gjggQYHcCXfuS9aN/8W /irRhC1mFNQcYuPDVHMXM9+PSJTqbVMUNr15g1dDq+v1XUvF09bW0qelSaKcjdNUTozE 8x0N+X7u5eTNv/epXKi3scUN4ddA/8GtXORnAfgz0KKaxF3GSwsyb3+FkWbYbm8I3PTA xMt7QS4kbkhnkXKmnujATLL27VJiIour4WSWz3Tx9dO48Ej/XT7BZryGdD5Cju5FwUo+ 0X/g==
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=pJ/tVTtwyTx+gneArooEfMYy80zoBRfXnwFMAqumtoU=; b=tLmGMFiZzUyNnGpNveRbtAOFCm26M9jMuBNRNNCzcEFnoYnXPE7ZorN7kp4wO4E9B+ /4gNMszCwM8BWpCEcBBvtRq/l20kt0mVEdS9mNmHpiTL+UWrwkeVSFTGXVSC/92njCpu j3gfK/l38a25KvyOKfIDGtVdyMiH71h1r1bfmP5FIGL6KnyZ1b/zWPWa5J3cEoCEpH+4 E1/0Zg5F+GOdZ7t00tNkGiwA3YD+3SOA5LkBctEvenLod/8gqKUg9MeS6ZOmRvJztqcC GCsvJrwwRvHY+WsGkG68T/fwFqx39plmB/QzY97uyXUgA0y8Hu2YjMOoTXDPYzP1+fuL hHsA==
X-Gm-Message-State: AOAM530PNFulnYlgN8jxT8JCCD2NI2QlYYFvuuyAMPlwIW/5NVMKTb4V NkA/hSZfk8fmt0AJjPuguV7GBdA0AxR3ev4thsk=
X-Google-Smtp-Source: ABdhPJxBjDgDmd6UKzxOKuaSMm94mq+RT6w4/st8oZE9t+BRoKWh5xoRCcOamSv/aaaEHQzBtw/adeRwlPzD2ClNh74=
X-Received: by 2002:a63:3441:: with SMTP id b62mr705083pga.191.1599006010135; Tue, 01 Sep 2020 17:20:10 -0700 (PDT)
MIME-Version: 1.0
References: <CAEMK1uY0cSOyyU2t0N9RTOzmMeEpfMsb7K9WfQD=fQdCde9jTQ@mail.gmail.com> <B2AA5092-32BD-499D-9EAF-09AB95E6E9B6@lodderstedt.net> <CAGBSGjoKfR1DpQ47oDPi8xqt_Bq54ywpTvZkH9uJwHRZkDbf-A@mail.gmail.com> <CAEMK1ubU0tD37yz0mKuOOP5n5uQ5pjLdLgY1OJWHGNh-iGcScw@mail.gmail.com> <dddbfebf-c5d0-6386-3a1d-c38526fdfba3@free.fr>
In-Reply-To: <dddbfebf-c5d0-6386-3a1d-c38526fdfba3@free.fr>
From: Dima Postnikov <dima@postnikov.net>
Date: Wed, 2 Sep 2020 10:19:58 +1000
Message-ID: <CAEMK1ubKn73gfM34yswmuAHzmOneXF9aRQ7uRnJ3DnNz56nZLA@mail.gmail.com>
To: Denis <denis.ietf@free.fr>
Cc: oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003a5a3305ae4999f3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/brctT3Buepq_TUR6RoUdnWmNf3Q>
Subject: Re: [OAUTH-WG] third party applications
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Sep 2020 00:20:13 -0000

Good point Denis, thanks

The OAuth 2.1 authorization framework enables a*n* *third-party*
application to obtain limited access to an HTTP service, either on
   behalf of a resource owner by orchestrating an approval interaction
   between the resource owner and the HTTP service, or by allowing the
   *third-party* application to obtain access on its own behalf.  This
   specification replaces and obsoletes the OAuth 2.0 Authorization
   Framework described in RFC 6749 <https://tools.ietf.org/html/rfc6749>.


And an additional section is required to describe scenarios where this
framework works well and scenarios when it doesn't.


On Wed, Sep 2, 2020 at 12:57 AM Denis <denis.ietf@free.fr> wrote:

> Hello Dima,
>
> Not exactly.
>
> Change :
>
> or by allowing the third-party application
>
> into:
>
>         or by allowing the application
>
>
> Denis
>
> Thank everyone for your feedback.
>
> So the abstract could look like this:
>
> The OAuth 2.1 authorization framework enables a*n* *third-party*   application to obtain limited access to an HTTP service, either on
>    behalf of a resource owner by orchestrating an approval interaction
>    between the resource owner and the HTTP service, or by allowing the
>    third-party application to obtain access on its own behalf.  This
>    specification replaces and obsoletes the OAuth 2.0 Authorization
>    Framework described in RFC 6749 <https://tools.ietf.org/html/rfc6749>.
>
>  And an additional section is required to describe scenarios where this framework works well and scenarios when it doesn't.
>
>
> On Sat, Aug 29, 2020 at 2:37 AM Aaron Parecki <aaron@parecki.com> wrote:
>
>> I agree. While the original motivations for OAuth were to support
>> third-party apps, it's proven to be useful in many other kinds of
>> situations as well, even when it's a "first-party" app but the OAuth server
>> is operated by a different organization than the APIs. I don't think the
>> abstract needs any qualification on this and would only confuse people
>> further. Any clarifications of which situations are appropriate for using
>> OAuth could be explored in a different section in the spec.
>>
>> Aaron Parecki
>>
>> On Fri, Aug 28, 2020 at 3:02 AM Torsten Lodderstedt <torsten=
>> 40lodderstedt.net@dmarc.ietf.org> wrote:
>>
>>> I agree. OAuth works for 3rd as well as 1st parties as well.
>>>
>>> > On 28. Aug 2020, at 05:26, Dima Postnikov <dima@postnikov.net> wrote:
>>> >
>>> > Hi,
>>> >
>>> > Can "third-party" term be removed from the specification?
>>> >
>>> > The standard and associated best practices apply to other applications
>>> that act on behalf of a resource owner, too (internal, "first-party" and
>>> etc).
>>> >
>>> > Regards,
>>> >
>>> > Dima
>>> >
>>> > The OAuth 2.1 authorization framework enables a third-party
>>> >
>>> >    application to obtain limited access to an HTTP service, either on
>>> >    behalf of a resource owner by orchestrating an approval interaction
>>> >    between the resource owner and the HTTP service, or by allowing the
>>> >    third-party application to obtain access on its own behalf.  This
>>> >    specification replaces and obsoletes the OAuth 2.0 Authorization
>>> >    Framework described in
>>> > RFC 6749.
>>> > _______________________________________________
>>> > OAuth mailing list
>>> > OAuth@ietf.org
>>> > https://www.ietf.org/mailman/listinfo/oauth
>>>
>>> _______________________________________________
>>> OAuth mailing list
>>> OAuth@ietf.org
>>> https://www.ietf.org/mailman/listinfo/oauth
>>>
>>
> _______________________________________________
> OAuth mailing listOAuth@ietf.orghttps://www.ietf.org/mailman/listinfo/oauth
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>