[OAUTH-WG] RFC 9126 on OAuth 2.0 Pushed Authorization Requests
rfc-editor@rfc-editor.org Wed, 15 September 2021 19:24 UTC
Return-Path: <wwwrun@rfc-editor.org>
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 15A843A08D8; Wed, 15 Sep 2021 12:24:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, 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 kxWc6MxfKvfA; Wed, 15 Sep 2021 12:24:03 -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 874D23A08A9; Wed, 15 Sep 2021 12:24:03 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A0937F40719; Wed, 15 Sep 2021 12:23:24 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210915192324.A0937F40719@rfc-editor.org>
Date: Wed, 15 Sep 2021 12:23:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/Tjrf4zgtbft_J6hVNLnXCSRC-bc>
Subject: [OAUTH-WG] RFC 9126 on OAuth 2.0 Pushed Authorization Requests
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, 15 Sep 2021 19:24:14 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9126
Title: OAuth 2.0 Pushed Authorization Requests
Author: T. Lodderstedt,
B. Campbell,
N. Sakimura,
D. Tonge,
F. Skokan
Status: Standards Track
Stream: IETF
Date: September 2021
Mailbox: torsten@lodderstedt.net,
bcampbell@pingidentity.com,
nat@sakimura.org,
dave@tonge.org,
panva.ip@gmail.com
Pages: 18
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-oauth-par-10.txt
URL: https://www.rfc-editor.org/info/rfc9126
DOI: 10.17487/RFC9126
This document defines the pushed authorization request (PAR)
endpoint, which allows clients to push the payload of an OAuth 2.0
authorization request to the authorization server via a direct
request and provides them with a request URI that is used as
reference to the data in a subsequent call to the authorization
endpoint.
This document is a product of the Web Authorization Protocol Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. 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