[OAUTH-WG] BCP 212, RFC 10017 on OAuth 2.0 for Browser-Based Applications
rfc-editor@rfc-editor.org Fri, 21 August 2026 21:37 UTC
Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: oauth@ietf.org
Delivered-To: oauth@mail2.ietf.org
Received: from celery-66557cc547-nndbf (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 5C23612D98EA2; Fri, 21 Aug 2026 14:37:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1787348260; bh=qO09pF5jat1TOTwCrY/pJCQeJiS7xfNyZY8zRF5ASUI=; h=Subject:From:To:Cc:Date; b=iLTG4bBDvIDpqny2Uc1UmFjKAaWFZPYrpYJ7CmUrcaqsc4IQ1QKp5TYECsCTIYuS1 mfa46FngR4qyY9XPz7iKDZKIZXHfhHJ60eCNUZQsaAkzgIIkeJ009sgxfOciPqgBLh 716zwrpl0WuOcA8k84gTXhHwVoICL2arQ3C3MUAY=
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: rfc-editor@rfc-editor.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Date: Fri, 21 Aug 2026 21:37:40 -0000
message-id: <178734826008.17.13680814862728007277@rfc-editor.org>
Message-ID-Hash: HQQV3I3NED4VJSF4VWBAD2TEC43CQ24A
X-Message-ID-Hash: HQQV3I3NED4VJSF4VWBAD2TEC43CQ24A
X-MailFrom: rfc-editor@rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-oauth.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, oauth@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [OAUTH-WG] BCP 212, RFC 10017 on OAuth 2.0 for Browser-Based Applications
List-Id: OAUTH WG <oauth.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/VxtwQa4eBrl1Xt9AngohL3BYAFo>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Owner: <mailto:oauth-owner@ietf.org>
List-Post: <mailto:oauth@ietf.org>
List-Subscribe: <mailto:oauth-join@ietf.org>
List-Unsubscribe: <mailto:oauth-leave@ietf.org>
A new Request for Comments is now available in online RFC libraries.
BCP 212
RFC 10017
Title: OAuth 2.0 for Browser-Based Applications
Author: A. Parecki,
P. De Ryck,
D. Waite
Status: Best Current Practice
Stream: IETF
Date: August 2026
Mailbox: aaron@parecki.com,
philippe@pragmaticwebsecurity.com,
dwaite@pingidentity.com
Pages: 49
I-D Tag: draft-ietf-oauth-browser-based-apps-26
URL: https://www.rfc-editor.org/info/rfc10017
DOI: 10.17487/RFC10017
This specification details the threats, attack consequences, security considerations,
and best practices that must be taken into account when developing browser-based
applications that use OAuth 2.0.
This document is a product of the Web Authorization Protocol Working Group of the IETF.
BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search/
For downloading RFCs, see https://www.rfc-editor.org/series/rfc-download/
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team