Re: [OAUTH-WG] Clarification: authorization server matching of redirect URI
Brian Eaton <beaton@google.com> Mon, 19 April 2010 17:23 UTC
Return-Path: <beaton@google.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 9A8F23A6AB5 for <oauth@core3.amsl.com>; Mon, 19 Apr 2010 10:23:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.977
X-Spam-Level:
X-Spam-Status: No, score=-101.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, USER_IN_WHITELIST=-100]
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 ZoMX0Y308sBP for <oauth@core3.amsl.com>; Mon, 19 Apr 2010 10:23:38 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id 03D723A6AE6 for <oauth@ietf.org>; Mon, 19 Apr 2010 10:16:34 -0700 (PDT)
Received: from kpbe15.cbf.corp.google.com (kpbe15.cbf.corp.google.com [172.25.105.79]) by smtp-out.google.com with ESMTP id o3JHGOvZ001460 for <oauth@ietf.org>; Mon, 19 Apr 2010 19:16:25 +0200
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1271697385; bh=ymZMAPMCnKaXDscuThJXuWRRhYg=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type:Content-Transfer-Encoding; b=nMoqzm4xfFgQUffz/2o54wxjKPl0UxN3sDd7suvpJOpQSDJxPJzrmyWy5iK9vuHQt qo1x7Xp0EjbwlphP+86uA==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:content-transfer-encoding:x-system-of-record; b=vsAYIYAGPK/Kegp8KlSlXpH+0x9L97h6bYaT/WYFYoeu37uBRnpva4lvBl0qkPhES VsSn3vGaBZoSxicrbxgig==
Received: from vws18 (vws18.prod.google.com [10.241.21.146]) by kpbe15.cbf.corp.google.com with ESMTP id o3JHFtfI023323 for <oauth@ietf.org>; Mon, 19 Apr 2010 10:16:23 -0700
Received: by vws18 with SMTP id 18so165306vws.27 for <oauth@ietf.org>; Mon, 19 Apr 2010 10:16:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.109.99 with HTTP; Mon, 19 Apr 2010 10:16:23 -0700 (PDT)
In-Reply-To: <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> <90C41DD21FB7C64BB94121FBBC2E723438E5C7F059@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Date: Mon, 19 Apr 2010 10:16:23 -0700
Received: by 10.220.108.228 with SMTP id g36mr3745053vcp.146.1271697383285; Mon, 19 Apr 2010 10:16:23 -0700 (PDT)
Message-ID: <o2jdaf5b9571004191016xdff990f6g92c78a1abad970fa@mail.gmail.com>
From: Brian Eaton <beaton@google.com>
To: Eran Hammer-Lahav <eran@hueniverse.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
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 17:23:42 -0000
On Mon, Apr 19, 2010 at 8:39 AM, Eran Hammer-Lahav <eran@hueniverse.com> wrote: >> 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. See page 9: http://trac.tools.ietf.org/wg/oauth/trac/attachment/wiki/SecurityConsiderations/OAuth%20WRAP%202.0%20Security%20Considerations.pdf Cheers, Brian
- [OAUTH-WG] Clarification: authorization server ma… Dick Hardt
- Re: [OAUTH-WG] Clarification: authorization serve… Eran Hammer-Lahav
- Re: [OAUTH-WG] Clarification: authorization serve… Dick Hardt
- Re: [OAUTH-WG] Clarification: authorization serve… Brian Eaton
- Re: [OAUTH-WG] Clarification: authorization serve… Eran Hammer-Lahav
- Re: [OAUTH-WG] Clarification: authorization serve… Brian Eaton
- Re: [OAUTH-WG] Clarification: authorization serve… Marius Scurtescu
- Re: [OAUTH-WG] Clarification: authorization serve… Eran Hammer-Lahav