IETF Logo Mail Archive

Re: [OAUTH-WG] redirect uri validation

Torsten Lodderstedt <torsten@lodderstedt.net> Mon, 25 July 2011 17:42 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 634BA22800E for <oauth@ietfa.amsl.com>; Mon, 25 Jul 2011 10:42:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.806
X-Spam-Level:
X-Spam-Status: No, score=-1.806 tagged_above=-999 required=5 tests=[AWL=-0.157, BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_102=0.6]
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 zGMSVcegYKKd for <oauth@ietfa.amsl.com>; Mon, 25 Jul 2011 10:42:06 -0700 (PDT)
Received: from smtprelay04.ispgateway.de (smtprelay04.ispgateway.de [80.67.18.16]) by ietfa.amsl.com (Postfix) with ESMTP id CBAA021F8C02 for <oauth@ietf.org>; Mon, 25 Jul 2011 10:42:05 -0700 (PDT)
Received: from [130.129.17.214] by smtprelay04.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from <torsten@lodderstedt.net>) id 1QlPAK-00083e-P5; Mon, 25 Jul 2011 19:42:04 +0200
Message-ID: <4E2DAAEA.7090304@lodderstedt.net>
Date: Mon, 25 Jul 2011 13:42:02 -0400
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: Eran Hammer-Lahav <eran@hueniverse.com>
References: <fcffd9492cbaced09c93f4e3c37b569f@lodderstedt-online.de> <90C41DD21FB7C64BB94121FBBC2E72345021F37877@P3PW5EX1MB01.EX1.SECURESERVER.NET>
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E72345021F37877@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Df-Sender: torsten@lodderstedt-online.de
Cc: "torsten@lodderstedt-online.de" <torsten@lodderstedt-online.de>, "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] redirect uri validation
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: Mon, 25 Jul 2011 17:42:06 -0000

Hi Eran,

>>> OAuth 1.0 was highly criticized for failing to address client identity
>>> in public clients. I believe OAuth 2.0 offers a much better story,
>>> within the boundaries>of what’s possible today.
>> Agreed. I think we must honestly discuss the value of client
>> authentication/identification itself. I personally think it is over-emphazised
>> right now. The strength of OAuth 2.0 is that it allows solutions where neither
>> client nor resource server have access or do store end-user credentials.
>> Client authentication is nice but not the main feature.
> Do you have any specific suggestions not already mentioned on the list?

I would suggest to mention that while an invalid redirect_uri indicates 
a counterfeit clients a valid redirect does not prove the calling 
client's identity.

regards,
Torsten.


> EHL
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

v2.23.0 | Report a Bug | By Email