Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-browser-based-apps-03.txt

Aaron Parecki <aaron@parecki.com> Wed, 24 July 2019 23:19 UTC

Return-Path: <aaron@parecki.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 9DEBD12006E for <oauth@ietfa.amsl.com>; Wed, 24 Jul 2019 16:19:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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=parecki-com.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 Qtkqdz95cUSP for <oauth@ietfa.amsl.com>; Wed, 24 Jul 2019 16:19:39 -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 AA27512027B for <oauth@ietf.org>; Wed, 24 Jul 2019 16:19:39 -0700 (PDT)
Received: by mail-io1-xd31.google.com with SMTP id h6so6676062iom.7 for <oauth@ietf.org>; Wed, 24 Jul 2019 16:19:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parecki-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=pIpWlkYRMUgGbMq/DNlRxcAmIgrKhJyK/Sl3NdEH8PA=; b=uL9O+hrvpxgG9/xCMZpOV90zi3hEzbskUHo89CA0R/P53A6mofnPqlAu74E2QOeKQt WF4W6fxdzKRsIkaVQuPCmv5lbs7NDipzhswGKtlal7BPY7WQylBB9c/W/e6pBksL1t7R 71a8mewgV1pRvsrlmP/9ydCKiGfmMVpkjT6TJWQPwMoQir9w+xzd128Wigf380t1JiU1 3FdDG+tOqd2vgdlgrv4zMrH2BeZLQtby0iPoytPuwhyeOdxxelsnuiF+bPKBz+VY8Rsp ETewbxdrlv36RY/VdhPX4TtFEz6s9Pag23eckZ62y46T+YzpajjRsI/gdwWJVeBOrHEN 72dw==
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; bh=pIpWlkYRMUgGbMq/DNlRxcAmIgrKhJyK/Sl3NdEH8PA=; b=taFxywjoYTgbDC4BAa462s5UrwiEAf0vXD7AzIY/V9IL9keA0z0anhZhSve+j+HmnH 9KMQ2i9E8UERSxT8f2sTYwNqkyxEoBUKzqUAK/4km1ip7/VwjlcGWBg5w62+aAnC+ld9 tZhKB+II6OA/bzR677ALyVITq3V+F9aIGp7+Y6P/x20LO8nKbQQnFfJ90OLBbZG2JpPB +annDsQ2pI7qEAKWE3LUEH3C0nag8rjGxSfVtx7qJTiSSNtl57U40GP6oPu9XP95r03k auiSZmbZioKGNZ56eZDx4ciNA/Wiwn/GvbnW3lJ/qAY8v2XbaXyrlLpBUVZfutGcm60Y uDeQ==
X-Gm-Message-State: APjAAAWxiHlNruH4NP1jBgoXRdrNWWinHyQHCR2QEHbJ8VpFHxHatIlt GQtMtp5xqqitTzu6KEm41YM9cDmYVoTlIA==
X-Google-Smtp-Source: APXvYqzusR/so+N0xOCDw2cHAYoJKEx25PcfHrdzIOvvhRJjm/cJJVsbBI/k0YDdZjeVCydgvcocOw==
X-Received: by 2002:a6b:bc42:: with SMTP id m63mr64034190iof.189.1564010378699; Wed, 24 Jul 2019 16:19:38 -0700 (PDT)
Received: from mail-io1-f54.google.com (mail-io1-f54.google.com. [209.85.166.54]) by smtp.gmail.com with ESMTPSA id m4sm42225231iok.68.2019.07.24.16.19.38 for <oauth@ietf.org> (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Wed, 24 Jul 2019 16:19:38 -0700 (PDT)
Received: by mail-io1-f54.google.com with SMTP id m24so93283754ioo.2 for <oauth@ietf.org>; Wed, 24 Jul 2019 16:19:38 -0700 (PDT)
X-Received: by 2002:a02:a07:: with SMTP id 7mr89191971jaw.65.1564010378155; Wed, 24 Jul 2019 16:19:38 -0700 (PDT)
MIME-Version: 1.0
References: <156401017666.14534.9422325088242867919@ietfa.amsl.com>
In-Reply-To: <156401017666.14534.9422325088242867919@ietfa.amsl.com>
From: Aaron Parecki <aaron@parecki.com>
Date: Wed, 24 Jul 2019 19:18:34 -0400
X-Gmail-Original-Message-ID: <CAGBSGjo97rjF=bV5A3p80e5Li+U9n7O9iRvEGj7OmmqVTvmuQA@mail.gmail.com>
Message-ID: <CAGBSGjo97rjF=bV5A3p80e5Li+U9n7O9iRvEGj7OmmqVTvmuQA@mail.gmail.com>
To: OAuth WG <oauth@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/gCuAJLL7kB54234smOqcLyttyiQ>
Subject: Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-browser-based-apps-03.txt
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, 24 Jul 2019 23:19:41 -0000

Hi all, thanks for the latest round of feedback. I've incorporated
these suggestions into the latest draft, -03. Here's a summary of the
changes since -02:

* Updated the historic note about the fragment URL clarifying that the
Session History API means browsers can use the unmodified
authorization code flow
* Rephrased "Authorization Code Flow" intro paragraph to better lead
into the next two sections
* Softened "is likely a better decision to avoid using OAuth entirely"
to "it may be..." for common-domain deployments
* Updated abstract to not be limited to public clients, since the
later sections talk about confidential clients
* Removed references to avoiding OpenID Connect for same-domain architectures
* Updated headers to better describe architectures (Apps Served from a
Static Web Server -> JavaScript Applications without a Backend)
* Expanded "same-domain architecture" section to better explain the
problems that OAuth has in this scenario
* Referenced Security BCP in implicit flow attacks where possible
* Minor typo corrections

I have a few open questions on this still based on discussion on the
list that there was not a clear consensus on, so I've prepared those
points to talk about during the session on Friday.

----
Aaron Parecki
aaronparecki.com
@aaronpk

----
Aaron Parecki
aaronparecki.com
@aaronpk



On Wed, Jul 24, 2019 at 7:17 PM <internet-drafts@ietf.org>; wrote:
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Web Authorization Protocol WG of the IETF.
>
>         Title           : OAuth 2.0 for Browser-Based Apps
>         Authors         : Aaron Parecki
>                           David Waite
>         Filename        : draft-ietf-oauth-browser-based-apps-03.txt
>         Pages           : 18
>         Date            : 2019-07-24
>
> Abstract:
>    This specification details the security considerations that must be
>    taken into account when developing browser-based applications, as
>    well as best practices for how they can securely implement OAuth 2.0.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-oauth-browser-based-apps/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-oauth-browser-based-apps-03
> https://datatracker.ietf.org/doc/html/draft-ietf-oauth-browser-based-apps-03
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-oauth-browser-based-apps-03
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth