[OAUTH-WG] Issue 16, revised Redirection URI section (3.1.2)
Torsten Lodderstedt <torsten@lodderstedt.net> Wed, 20 July 2011 21:15 UTC
Return-Path: <torsten@lodderstedt.net>
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 C5EDF21F88A0 for <oauth@ietfa.amsl.com>; Wed, 20 Jul 2011 14:15:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.034
X-Spam-Level:
X-Spam-Status: No, score=-2.034 tagged_above=-999 required=5 tests=[AWL=0.215, BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vjbMUcWoHcwS for <oauth@ietfa.amsl.com>; Wed, 20 Jul 2011 14:15:01 -0700 (PDT)
Received: from smtprelay03.ispgateway.de (smtprelay03.ispgateway.de [80.67.31.41]) by ietfa.amsl.com (Postfix) with ESMTP id 4825121F851A for <oauth@ietf.org>; Wed, 20 Jul 2011 14:15:01 -0700 (PDT)
Received: from [79.253.8.100] (helo=[192.168.71.35]) by smtprelay03.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from <torsten@lodderstedt.net>) id 1Qje6d-0005Fw-Qr for oauth@ietf.org; Wed, 20 Jul 2011 23:14:59 +0200
Message-ID: <4E274554.5070606@lodderstedt.net>
Date: Wed, 20 Jul 2011 23:15:00 +0200
From: Torsten Lodderstedt <torsten@lodderstedt.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: OAuth WG <oauth@ietf.org>
Content-Type: text/plain; charset="ISO-8859-15"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Df-Sender: torsten@lodderstedt-online.de
Subject: [OAUTH-WG] Issue 16, revised Redirection URI section (3.1.2)
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 20 Jul 2011 21:15:01 -0000
"The authorization server redirects the user-agent to the client's redirection URI previously established with the authorization server during the client registration process." Conflicts with section 3.1.2.3, which allows to pass a redirect_uri via URI query parameter. 3.1.2.1 Endpoint Confidentiality What does "endpoint" confidentiality mean? Which endpoint does this text refer to? The client's redirect_uri endpoint? The text, in my opinion, covers two different scenarios: first paragraph: confidentiality of access tokens and authz codes in transit. second paragraph/last sentence: men-in-the-middle attacks Those attacks are also covered in sections 10.5 and 10.8. 3.1.2.5. Endpoint Content As this section discusses security aspects of the client's implementation of the redirect_uri page, shouldn't this go to the security considerations section? regards, Torsten.
- [OAUTH-WG] Issue 16, revised Redirection URI sect… Torsten Lodderstedt
- Re: [OAUTH-WG] Issue 16, revised Redirection URI … Eran Hammer-Lahav
- Re: [OAUTH-WG] Issue 16, revised Redirection URI … Torsten Lodderstedt
- Re: [OAUTH-WG] Issue 16, revised Redirection URI … Eran Hammer-Lahav
- Re: [OAUTH-WG] Issue 16, revised Redirection URI … Torsten Lodderstedt
- Re: [OAUTH-WG] Issue 16, revised Redirection URI … Eran Hammer-Lahav