BCP 212, RFC 8252 on OAuth 2.0 for Native Apps
rfc-editor@rfc-editor.org Wed, 04 October 2017 17:04 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E57913422B; Wed, 4 Oct 2017 10:04:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 M8V4wAXNCF2j; Wed, 4 Oct 2017 10:04:46 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92B11133341; Wed, 4 Oct 2017 10:04:46 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 783C2B81F32; Wed, 4 Oct 2017 10:04:41 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 212, RFC 8252 on OAuth 2.0 for Native Apps
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, oauth@ietf.org
Message-Id: <20171004170441.783C2B81F32@rfc-editor.org>
Date: Wed, 04 Oct 2017 10:04:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/T2NL58GxKCTCDMhVmsSnDSKbY3w>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Oct 2017 17:04:48 -0000
A new Request for Comments is now available in online RFC libraries.
BCP 212
RFC 8252
Title: OAuth 2.0 for Native Apps
Author: W. Denniss,
J. Bradley
Status: Best Current Practice
Stream: IETF
Date: October 2017
Mailbox: rfc8252@wdenniss.com,
rfc8252@ve7jtb.com
Pages: 21
Characters: 49680
Updates: RFC 6749
See Also: BCP 212
I-D Tag: draft-ietf-oauth-native-apps-12.txt
URL: https://www.rfc-editor.org/info/rfc8252
DOI: 10.17487/RFC8252
OAuth 2.0 authorization requests from native apps should only be made
through external user-agents, primarily the user's browser. This
specification details the security and usability reasons why this is
the case and how native apps and authorization servers can implement
this best practice.
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/retrieve/bulk
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
Association Management Solutions, LLC