IETF Logo Mail Archive

Re: [OAUTH-WG] Clarification: authorization server matching of redirect URI

Eran Hammer-Lahav <eran@hueniverse.com> Mon, 19 April 2010 15:59 UTC

Return-Path: <eran@hueniverse.com>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5C89328C2A0 for <oauth@core3.amsl.com>; Mon, 19 Apr 2010 08:59:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.461
X-Spam-Level:
X-Spam-Status: No, score=-2.461 tagged_above=-999 required=5 tests=[AWL=0.138, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3gz70I5I2XEm for <oauth@core3.amsl.com>; Mon, 19 Apr 2010 08:59:24 -0700 (PDT)
Received: from p3plex1out02.prod.phx3.secureserver.net (p3plex1out02.prod.phx3.secureserver.net [72.167.180.18]) by core3.amsl.com (Postfix) with SMTP id 665633A6AE6 for <oauth@ietf.org>; Mon, 19 Apr 2010 08:39:50 -0700 (PDT)
Received: (qmail 31897 invoked from network); 19 Apr 2010 15:39:42 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.19) by p3plex1out02.prod.phx3.secureserver.net with SMTP; 19 Apr 2010 15:39:42 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT001.EX1.SECURESERVER.NET ([72.167.180.19]) with mapi; Mon, 19 Apr 2010 08:39:38 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Brian Eaton <beaton@google.com>, Dick Hardt <dick.hardt@gmail.com>
Date: Mon, 19 Apr 2010 08:39:42 -0700
Thread-Topic: [OAUTH-WG] Clarification: authorization server matching of redirect URI
Thread-Index: Acrf1jdEVM0J3wFWTM2QR1T3y5SNogAACMSQ
Message-ID: <90C41DD21FB7C64BB94121FBBC2E723438E5C7F059@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <2997F829-4755-44A8-ADD5-643BCE25AA61@gmail.com> <90C41DD21FB7C64BB94121FBBC2E723438E30A379C@P3PW5EX1MB01.EX1.SECURESERVER.NET> <65D588CD-A374-4F6B-8749-199C5DF83300@gmail.com> <x2kdaf5b9571004190836l2595e181obdb977045e11c49e@mail.gmail.com>
In-Reply-To: <x2kdaf5b9571004190836l2595e181obdb977045e11c49e@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Clarification: authorization server matching of redirect URI
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 19 Apr 2010 15:59:25 -0000

> -----Original Message-----
> From: Brian Eaton [mailto:beaton@google.com]
> Sent: Monday, April 19, 2010 8:37 AM
> To: Dick Hardt
> Cc: Eran Hammer-Lahav; OAuth WG
> Subject: Re: [OAUTH-WG] Clarification: authorization server matching of
> redirect URI
> 
> On Sun, Apr 18, 2010 at 10:35 PM, Dick Hardt <dick.hardt@gmail.com> wrote:
> > The spec should describe how the redirect URI is verified to what is
> registered. I can enumerate the options for discussion adding in the state
> parameter as an option.
> 
> Note that there are two spots where the AS does some URI matching.
> 
> The first is before redirecting the user to the callback URI.  This seems
> doomed to being service provider specific, unfortunately.

I agree. If someone wants to suggest some security consideration text that would be good.

> The second is when exchanging the verification code for the refresh token
> and access token.  This can always be a string equality match.

It should be a case-sensitive string comparison with the value provided by the client in the first step.

EHL

v2.23.0 | Report a Bug | By Email