Re: [OAUTH-WG] third party applications

Dima Postnikov <dima@postnikov.net> Tue, 01 September 2020 13:59 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 8BD703A08B1 for <oauth@ietfa.amsl.com>; Tue, 1 Sep 2020 06:59:29 -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 kPfM81wcN-N3 for <oauth@ietfa.amsl.com>; Tue, 1 Sep 2020 06:59:28 -0700 (PDT)
Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) (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 1B28E3A08AE for <oauth@ietf.org>; Tue, 1 Sep 2020 06:59:28 -0700 (PDT)
Received: by mail-pj1-x1031.google.com with SMTP id 2so660959pjx.5 for <oauth@ietf.org>; Tue, 01 Sep 2020 06:59:28 -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=V8tkfke6XRFJXKrLkE3xePN/ixiGz+TQ5mjXrhutmZc=; b=cJfE7MvIUtoe66Ur/1n1/sOeEGleVqfPdw4Fj9hfDpeHoW9PobsELEit6tx/bucHds JQLXWWrgg3DEGnHI/gx1bW3uUL/qZcklZkrWayE/7tIIuJhXjLyfZ0bXRes4TnlwmB2Q 24ROdjyKqA0qobqlYkEzmYKMfgvKU6pHqdyaqIu6RGO0SwXuiu+lKVsLINVNA3wUShie rPuuGurLRIsV2AhHgxCckprmJFueeacZe5qVSI2lZqqzvqyJaTmJ/lZ8S1eWf1UQsTOI iJAI9P+oeMAf4mJTHT21KgcmYBFljIURfowgI4ZKOMINBj5BHlE8O3S9QdMoGc3QXWIJ HDfA==
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=V8tkfke6XRFJXKrLkE3xePN/ixiGz+TQ5mjXrhutmZc=; b=EF4nEvU55jjTasBdnkjlnAZsF7hgfRbCYiXxrY1s1QUOGs8Wld5ezT3Lob592Gv4Yw edp9AF+MHIitAzhjfxdsvP5b3Z8OjWV+xD9rURR38jbryAtNs9fbQIHTJIWn3Taqj7qx Th+XtONpnXLb9i13/dKhAtiM58vUFQ4nthsTrvtvNwh2w1z4dQVLemZoiWYb1vZa+uBy U66lGbo0f9dpLhi91VENw19RVbBP1SEeXac/BBbNvzs2NrweMVGH+OOnvtGpvPWnm32g nrIpxqHX9eRXvbmRwz0zOU3F+I3ENlWKFFIzsFYn7c0wBY6toj8Vl+ZO1sqyECkrEZAC UJPw==
X-Gm-Message-State: AOAM530VGN3Iyy883V5wmII0lJy3jsHO1SrqJb+N4rr+E66jQ3frIDlh ZnrKOKZyeVl41KRMc5VIz1kmcXXKftvjGVhbhYQ=
X-Google-Smtp-Source: ABdhPJwSQ63VfaxVa9rFB8ZmVsp/thgSI+DWcuh4b29iUPyRjMnA3tSyLwvrfTS49AqdQIH5JvWCATHkalRUyx2QUqM=
X-Received: by 2002:a17:90a:bc94:: with SMTP id x20mr1665040pjr.16.1598968767495; Tue, 01 Sep 2020 06:59:27 -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>
In-Reply-To: <CAGBSGjoKfR1DpQ47oDPi8xqt_Bq54ywpTvZkH9uJwHRZkDbf-A@mail.gmail.com>
From: Dima Postnikov <dima@postnikov.net>
Date: Tue, 1 Sep 2020 23:59:15 +1000
Message-ID: <CAEMK1ubU0tD37yz0mKuOOP5n5uQ5pjLdLgY1OJWHGNh-iGcScw@mail.gmail.com>
To: Aaron Parecki <aaron@parecki.com>
Cc: Torsten Lodderstedt <torsten=40lodderstedt.net@dmarc.ietf.org>, oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000064c37c05ae40ed8a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/QGRAmNNzfkBJsMvSMmOmHAywPNo>
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: Tue, 01 Sep 2020 13:59:30 -0000

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
>>
>