IETF Logo Mail Archive

Re: [OAUTH-WG] Call for Adoption: OAuth 2.0 for Browser-Based Apps

Daniel Fett <danielf+oauth@yes.com> Wed, 19 December 2018 08:20 UTC

Return-Path: <danielf+oauth@yes.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 82CA1130DEB for <oauth@ietfa.amsl.com>; Wed, 19 Dec 2018 00:20:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yes.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 r-S08g8u6Opj for <oauth@ietfa.amsl.com>; Wed, 19 Dec 2018 00:20:41 -0800 (PST)
Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (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 AC7DE130DC8 for <oauth@ietf.org>; Wed, 19 Dec 2018 00:20:40 -0800 (PST)
Received: by mail-wm1-x334.google.com with SMTP id m22so5384852wml.3 for <oauth@ietf.org>; Wed, 19 Dec 2018 00:20:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yes.com; s=google; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=Ku0j/cK9VkmrzByJoQGS/dTMexLP/rrlbSDnOfsAwR0=; b=ZT26kuS6IzJG5TIsXx196e/WkQhX1cMZjQAsBHG+uRJoYoPA/0dPsEvlEb9Q292GI+ Z2dHyl5yuyoyQDQeDvYMMq3jeoSmh7QYj8C/5X7OEJf0N0g6YauWB1wEhKrG12ie0uO1 ka30ZkrmJsSjtToc32ZOzsO7pZvcZ5/TBq/p9fhExzhDTUqU30qYOofxubwJB73qYjJZ /8+5FnuK3LQcjkL7MV6gVOSQ/s/xovMkEdcn1YtfxyEndsBvQURW0tTzGrcYMsLk3ZuJ ESacfHAnwMEXk8iZW+RCvcvmbN69HdioiM+7t6clRyXsgxI8ByvF+7uHz33CIXtaQ1pY 31TQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=Ku0j/cK9VkmrzByJoQGS/dTMexLP/rrlbSDnOfsAwR0=; b=DqSEKE0klvAD56zTdbrXDcnhbhSQt8I/T7pc0NIEmnRwGpBpivzlvpH02sqJEKqgI3 ERpWbT3h97AFp31y/3N1Zz/KIF3F9+vBBWHinQpay/BezlIDAK4iCIaOKGVybN+wrARx Siy6sWxNKK8Sjl8bJzn7iUozjXIADpr5gQnoCx931NYhSx9mBuv67u/3i8J9CsKi1q9I JJ5JWtB4o5KZQv260x+TYY976IPh8ooLToR0ZLJjOUV7aYiJutpcBsCWuv5jWULLPNM9 kP7FSLznig5OTgfKWvguCoIQrbJNk4LPcpVmjeoLilrjtj7M0Sqjv4+8JHQ7MCxp1cl2 IebA==
X-Gm-Message-State: AA+aEWYbWMccV9ErM5eB5c3aoSKTW8XejiGX+PRqQib5jSyZg40WO099 Fq8rVP0OCdprG1UdBMksCF2p518L9btF4w==
X-Google-Smtp-Source: AFSGD/Urwr6Q3sMlCHhK9ABQpJKi5gqZb3yasGMtCx8Z4kxFPUeUM3G2anjz55HMBIo6JtGF1/2UiA==
X-Received: by 2002:a1c:a755:: with SMTP id q82mr6449199wme.6.1545207638791; Wed, 19 Dec 2018 00:20:38 -0800 (PST)
Received: from ?IPv6:2003:c1:4f01:c300:5907:efe:5f7f:84e2? (p200300C14F01C30059070EFE5F7F84E2.dip0.t-ipconnect.de. [2003:c1:4f01:c300:5907:efe:5f7f:84e2]) by smtp.gmail.com with ESMTPSA id l197sm11651002wma.44.2018.12.19.00.20.37 for <oauth@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Dec 2018 00:20:38 -0800 (PST)
To: oauth@ietf.org
References: <VI1PR0801MB211211AA90A5B25505DDA9BAFABC0@VI1PR0801MB2112.eurprd08.prod.outlook.com> <DB715BEA-3C0D-4585-8FAB-B3D809430758@lodderstedt.net>
From: Daniel Fett <danielf+oauth@yes.com>
Message-ID: <36ac942f-72f8-f3c7-5eda-43bc2a22beac@yes.com>
Date: Wed, 19 Dec 2018 09:20:36 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: <DB715BEA-3C0D-4585-8FAB-B3D809430758@lodderstedt.net>
Content-Type: multipart/alternative; boundary="------------D4B05DA258E97767913CF1E4"
Content-Language: de-DE
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/lIy-KcUPHzqymfo62Q9iw6SDFZI>
Subject: Re: [OAUTH-WG] Call for Adoption: OAuth 2.0 for Browser-Based Apps
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, 19 Dec 2018 08:20:43 -0000

Hi all,

Am 18.12.18 um 19:14 schrieb Torsten Lodderstedt:
> Hi Hannes, 
>
> while I think the current text needs some substantial work, I support the adoption of this draft as a working group document. I also think we need to carefully define the boundaries between the Security BCP and the SPA BCP in order to prevent unnecessary duplications and inconsistencies.


+1


> General remark: I would suggest to restructure section 6 to describe the potential architectures this BCP has in mind. From my perspective these are:
> - "pure" SPA
> - SPA w/ backend
> - SPA w/o OAuth (as fallback)

This distinction is very important and should not be discussed in
Section 6, but in the beginning of the document.


-Daniel

v2.23.0 | Report a Bug | By Email