[OAUTH-WG] [Technical Errata Reported] RFC6749 (3880)
RFC Errata System <rfc-editor@rfc-editor.org> Tue, 04 February 2014 16:13 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 801B01A013B for <oauth@ietfa.amsl.com>; Tue, 4 Feb 2014 08:13:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.953
X-Spam-Level:
X-Spam-Status: No, score=0.953 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 M6YpBOnH6VAL for <oauth@ietfa.amsl.com>; Tue, 4 Feb 2014 08:13:40 -0800 (PST)
Received: from rfc-editor.org (unknown [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id 6E9961A0130 for <oauth@ietf.org>; Tue, 4 Feb 2014 08:13:40 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 9A4007FC168; Tue, 4 Feb 2014 08:13:38 -0800 (PST)
To: dick.hardt@gmail.com, stephen.farrell@cs.tcd.ie, turners@ieca.com, Hannes.Tschofenig@gmx.net, derek@ihtfp.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20140204161338.9A4007FC168@rfc-editor.org>
Date: Tue, 04 Feb 2014 08:13:38 -0800
Cc: eriksencosta@gmail.com, oauth@ietf.org, rfc-editor@rfc-editor.org
Subject: [OAUTH-WG] [Technical Errata Reported] RFC6749 (3880)
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 04 Feb 2014 16:13:41 -0000
The following errata report has been submitted for RFC6749, "The OAuth 2.0 Authorization Framework". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=6749&eid=3880 -------------------------------------- Type: Technical Reported by: Eriksen Costa <eriksencosta@gmail.com> Section: 10.16 Original Text ------------- For public clients using implicit flows, this specification does not provide any method for the client to determine what client an access token was issued to. Corrected Text -------------- For public clients using implicit flows, this specification does not provide any method for the authorization server to determine what client an access token was issued to. Notes ----- A client can only know about tokens issued to it and not for other clients. Instructions: ------------- This errata is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC6749 (draft-ietf-oauth-v2-31) -------------------------------------- Title : The OAuth 2.0 Authorization Framework Publication Date : October 2012 Author(s) : D. Hardt, Ed. Category : PROPOSED STANDARD Source : Web Authorization Protocol Area : Security Stream : IETF Verifying Party : IESG
- [OAUTH-WG] [Technical Errata Reported] RFC6749 (3… RFC Errata System
- Re: [OAUTH-WG] [Technical Errata Reported] RFC674… Dick Hardt
- Re: [OAUTH-WG] [Technical Errata Reported] RFC674… John Bradley
- Re: [OAUTH-WG] [Technical Errata Reported] RFC674… Phil Hunt
- Re: [OAUTH-WG] [Technical Errata Reported] RFC674… Dick Hardt
- Re: [OAUTH-WG] [Technical Errata Reported] RFC674… Prateek Mishra
- Re: [OAUTH-WG] [Technical Errata Reported] RFC674… Bill Mills
- Re: [OAUTH-WG] [Technical Errata Reported] RFC674… John Bradley
- [OAUTH-WG] Suitable grant type for a Javascript u… philip.kershaw
- Re: [OAUTH-WG] Suitable grant type for a Javascri… Manfred Steyer
- Re: [OAUTH-WG] Suitable grant type for a Javascri… philip.kershaw
- Re: [OAUTH-WG] Suitable grant type for a Javascri… Prateek Mishra
- Re: [OAUTH-WG] Suitable grant type for a Javascri… Justin Richer
- Re: [OAUTH-WG] Suitable grant type for a Javascri… Prateek Mishra
- Re: [OAUTH-WG] Suitable grant type for a Javascri… John Bradley
- Re: [OAUTH-WG] Suitable grant type for a Javascri… philip.kershaw
- Re: [OAUTH-WG] Suitable grant type for a Javascri… John Bradley
- Re: [OAUTH-WG] Suitable grant type for a Javascri… philip.kershaw
- Re: [OAUTH-WG] Suitable grant type for a Javascri… John Bradley
- Re: [OAUTH-WG] [Technical Errata Reported] RFC674… Eriksen Costa
- [OAUTH-WG] [Errata Rejected] RFC6749 (3880) RFC Errata System