Re: [OAUTH-WG] OAuth for Browser-Based Apps Draft 12
Aaron Parecki <aaron@parecki.com> Wed, 07 December 2022 23:41 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 4E476C14CF05 for <oauth@ietfa.amsl.com>; Wed, 7 Dec 2022 15:41:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=parecki.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RBURgcKZPCrw for <oauth@ietfa.amsl.com>; Wed, 7 Dec 2022 15:41:08 -0800 (PST)
Received: from mail-vs1-xe32.google.com (mail-vs1-xe32.google.com [IPv6:2607:f8b0:4864:20::e32]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3A3FC1516E9 for <oauth@ietf.org>; Wed, 7 Dec 2022 15:41:03 -0800 (PST)
Received: by mail-vs1-xe32.google.com with SMTP id m4so18805915vsc.6 for <oauth@ietf.org>; Wed, 07 Dec 2022 15:41:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parecki.com; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=94C/pp9T2SON+489oF0Qt2hcI8LCAcaOBz8yLurZ44I=; b=RhQ+d3PzwaY/BSjEH4oRaUK/AN2KoB74FkHZktZFIDMsvzTSHDD2SGp2N73Z1UhEXb LgFktLDEuOddGwB66x0F6EKSqfR3/z3y3/RdPc712VB2iy8eOyAPVaTPjD572tbCpsom 5gT0Mr5ylFkr5+mDtYR4TYDi+pxaRQQumRzIA16+amcgb7RDAMukxgQtYQqE9cDMg1+z vCz6KhslShxl4VqOwo8h+Xa0effF1KlLhtJSZljbohCcydu7v1pQoGnIPwADObHCzsOt a5UT2XnDg25gvNolKs7KKk1YtoVoikBuQZBeW+he5tmGNIKM9f29z0vLxL5wKlOh+w3q H79Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=94C/pp9T2SON+489oF0Qt2hcI8LCAcaOBz8yLurZ44I=; b=wT27K3bsr/uVxDKwUYjurgbmogk2fGeKgeboQKwR7/g4f7ivIdEdm3XhYuvi3X9fSL sbTyl5yqNeKkfhZqxGo1lQ8BJ8SHlziOe7xonLXYV6k9a+7FuZ6hzgz2peQdmr9hRgsb XJa2wgTVgC5ZVXel2PB7I0IZbRG9OyjPUHX+mbtYTGNypoyV9JLeVJHiCsTeeKSRT+Gs Fa1ECaJT77uBePC2v2U4ATFzirPSQZ/PdSDTcuCsp/kNu4RNX03WMYwpFscXfoJ3o5AA I7K6v/JsDSYPd0x55WdBGrS3YERJ3CUY2ZlP/K+T+NTtMScBgYE4aI2dn+CvarQFB/Gd Wa0g==
X-Gm-Message-State: ANoB5pkFpb5nfirNu3zZuoPeYHLFppZu1cSPJ5b6zNtxjosCW6HI24IO WYhGIeyXWABiPRjcXXjQdp0Fw6dKd6NXiHNC
X-Google-Smtp-Source: AA0mqf4yVtFlP0BCeQ11m3KAo3qxZTq9q64nHcb3tmpKP/s6oxj1voyFiLzLPv09P6pKq/rVIrHyqQ==
X-Received: by 2002:a05:6102:3e8d:b0:3a8:3e42:ef9f with SMTP id m13-20020a0561023e8d00b003a83e42ef9fmr818059vsv.25.1670456461664; Wed, 07 Dec 2022 15:41:01 -0800 (PST)
Received: from mail-vk1-f177.google.com (mail-vk1-f177.google.com. [209.85.221.177]) by smtp.gmail.com with ESMTPSA id r9-20020a05610204a900b003a58dfea684sm2871881vsa.12.2022.12.07.15.41.00 for <oauth@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 07 Dec 2022 15:41:00 -0800 (PST)
Received: by mail-vk1-f177.google.com with SMTP id 6so9006653vkk.6 for <oauth@ietf.org>; Wed, 07 Dec 2022 15:41:00 -0800 (PST)
X-Received: by 2002:a05:6122:1784:b0:3ae:beb7:c880 with SMTP id o4-20020a056122178400b003aebeb7c880mr40933431vkf.38.1670456460418; Wed, 07 Dec 2022 15:41:00 -0800 (PST)
MIME-Version: 1.0
References: <167036996045.32057.8617864278204705226@ietfa.amsl.com> <CAGBSGjosYKJXVaJSN9B5ZFFB4B9h0wogQ9auQN4wm3dSqkZe_g@mail.gmail.com> <CAEayHEMRwPiexS79Gw9_Ew=_dL0TmBA7dnZgBum4XVq_94nXtA@mail.gmail.com>
In-Reply-To: <CAEayHEMRwPiexS79Gw9_Ew=_dL0TmBA7dnZgBum4XVq_94nXtA@mail.gmail.com>
From: Aaron Parecki <aaron@parecki.com>
Date: Wed, 07 Dec 2022 15:40:49 -0800
X-Gmail-Original-Message-ID: <CAGBSGjpBTaQO7X6e4Ar6Xm1DfwwtsVtdrdW7LvB9FJ0+dPqD5g@mail.gmail.com>
Message-ID: <CAGBSGjpBTaQO7X6e4Ar6Xm1DfwwtsVtdrdW7LvB9FJ0+dPqD5g@mail.gmail.com>
To: Thomas Broyer <t.broyer@gmail.com>
Cc: OAuth WG <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000efa85105ef45739a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/iwR8n5gdFKH3dJpdqPqFHDP11Z0>
Subject: Re: [OAUTH-WG] OAuth for Browser-Based Apps Draft 12
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.39
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, 07 Dec 2022 23:41:12 -0000
Thank you, you're absolutely correct. I've updated a few uses of that to something hopefully more accurate. There are a few more uses of "DOM" still and I would love someone who has more experience with browsers than me to review those for accuracy as well! Thanks! Latest editor's draft: https://drafts.oauth.net/oauth-browser-based-apps/draft-ietf-oauth-browser-based-apps.html Aaron On Wed, Dec 7, 2022 at 12:52 AM Thomas Broyer <t.broyer@gmail.com> wrote: > > > On Wed, Dec 7, 2022 at 1:07 AM Aaron Parecki <aaron= > 40parecki.com@dmarc.ietf.org> wrote: > >> Hi all, >> >> I just published a revised version of OAuth for Browser-Based Apps based >> on the feedback and discussion at IETF 115 London! >> >> >> https://www.ietf.org/archive/id/draft-ietf-oauth-browser-based-apps-12.html >> >> The primary changes are: >> >> * Rephrased the architecture patterns to focus on token acquisition >> > > Terminology-wise, the phrasing "code executed in the DOM" is not correct: > the DOM is an API for manipulating the document. This should rather be > "code executed in a browsing context" or possibly "code executed in a > document context" (or just "in a document"?), as opposed to a "worker > context" or service worker. > > Anyway, thanks for that work. I'm only using the drafts as reference in > architecture discussions and am looking forward to this turning into an RFC. > -- > Thomas Broyer > /tɔ.ma.bʁwa.je/ <http://xn--nna.ma.xn--bwa-xxb.je/> >
- [OAUTH-WG] I-D Action: draft-ietf-oauth-browser-b… internet-drafts
- [OAUTH-WG] OAuth for Browser-Based Apps Draft 12 Aaron Parecki
- Re: [OAUTH-WG] OAuth for Browser-Based Apps Draft… Thomas Broyer
- Re: [OAUTH-WG] OAuth for Browser-Based Apps Draft… Aaron Parecki