Re: [OAUTH-WG] third party applications

William Denniss <wdenniss@google.com> Wed, 02 September 2020 03:58 UTC

Return-Path: <wdenniss@google.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 1F5793A0B02 for <oauth@ietfa.amsl.com>; Tue, 1 Sep 2020 20:58:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level:
X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 HwUZvkZARF8X for <oauth@ietfa.amsl.com>; Tue, 1 Sep 2020 20:58:32 -0700 (PDT)
Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (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 BF2813A0AFA for <oauth@ietf.org>; Tue, 1 Sep 2020 20:58:31 -0700 (PDT)
Received: by mail-wm1-x332.google.com with SMTP id z9so3064903wmk.1 for <oauth@ietf.org>; Tue, 01 Sep 2020 20:58:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=A5X+rSRjE6uHeN8EjTMUej5VZ1Ftyzua55TbwCrSrac=; b=c+O4eKwwNBN/jVIE5h4IT6cgFT7yTc/3s27yavhNbJqCiZnFT3jfF8XQYUVnV4Pnhp hcxj4LmvnuEYhniup+aREM4OMbYznGBPaJvgi3p/7Twv4bgWVrwpd8/QNJm/AoN+XRhg GVeLYAjvVBLZUs8PBT1FP1hiz4DvTQgOckr7zipvFMRCUnDRCRG2NVnSQEDafKFj6UcR COwc79oWfqa4yVCmVTrlfWn214MuJA/nz4bKi6Md1TEdbRgahyRBdl7Yta0OMpfffRNS yZ05/Oldjkt0HxNyneo/TiDTs/J+1wI0a952eQlpMoU5ji7qWbAByOl9XcpQ1PRLNoac zplw==
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=A5X+rSRjE6uHeN8EjTMUej5VZ1Ftyzua55TbwCrSrac=; b=qBk3kNnBscs2cr/sFzvjKHYV+VsKMAjCz9g35bj1kxt2R1H0zKqEliRvqxFkQeEoGs Ps4icVUjX8BxOK0NiZgyCBXh8HAYZTgCeT+HtUia//b26zs8TIVk8bXibAYwZZav3WRc c6mKplFQ6VuSWRJ/CY6vbd8DRhdtLKUq8z5IdFD4JgIjqxDB9oIMmKnFRRPPMmSfgx7s v+I+Vf9Cr6Ry9SC1wOAZ3Rxf+2frw5qc52XVQuLCbq1AIe/By6rYaCvy1wHIGuw2vqxD 627ogZUGiapYguai8m0/ErOwLjBAugQBW7ryeZ4uyAlQzrIm+i7oKz+XsaVc4CS5jY3k ceCA==
X-Gm-Message-State: AOAM533n0X4B96Ohx2UQ2z/ohJhIBxKrup2YjiG+vvD2TPbKC6tklndn JO9OcakySSuYSolUl/Y8diFRbItDdfmi0vDCvG4ZNg==
X-Google-Smtp-Source: ABdhPJwdEcU6a+/hO7VHf6nkxmikGWLeIsL/WL8H1MvyF0u/IKemZ1izk69qVU9fQefHI41/nA5W7/cZ5NAQsynG8Sw=
X-Received: by 2002:a1c:cc0d:: with SMTP id h13mr4532099wmb.44.1599019109673; Tue, 01 Sep 2020 20:58:29 -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> <CAEMK1ubKn73gfM34yswmuAHzmOneXF9aRQ7uRnJ3DnNz56nZLA@mail.gmail.com>
In-Reply-To: <CAEMK1ubKn73gfM34yswmuAHzmOneXF9aRQ7uRnJ3DnNz56nZLA@mail.gmail.com>
From: William Denniss <wdenniss@google.com>
Date: Tue, 1 Sep 2020 20:58:18 -0700
Message-ID: <CAAP42hAsrPvE-bMLdYhkvX516wBKMwCjNJaOhcZ14LQPr+Eh7A@mail.gmail.com>
To: Dima Postnikov <dima@postnikov.net>
Cc: Denis <denis.ietf@free.fr>, oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000005c6fd05ae4ca639"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/o0kHY0OXrglm83Z7BffxP5txabI>
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 03:58:34 -0000

+1 to drop the "third party", there are valid first party use-cases.

On the subject, in first party cases the access may not be all that
"limited", I wonder if it should read more genericly "an application to
obtain access to an HTTP service"?

On Tue, Sep 1, 2020 at 5:20 PM Dima Postnikov <dima@postnikov.net> wrote:

> 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
>>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>