IETF Logo Mail Archive

Re: [OAUTH-WG] User-agent flow and pre-registered redirect_uri

Marius Scurtescu <mscurtescu@google.com> Tue, 08 June 2010 01:23 UTC

Return-Path: <mscurtescu@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 A6BFC3A68E9 for <oauth@core3.amsl.com>; Mon, 7 Jun 2010 18:23:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.563
X-Spam-Level:
X-Spam-Status: No, score=-103.563 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, 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 1Xexm4OE-ug9 for <oauth@core3.amsl.com>; Mon, 7 Jun 2010 18:23:32 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 938F33A68E0 for <oauth@ietf.org>; Mon, 7 Jun 2010 18:23:32 -0700 (PDT)
Received: from hpaq5.eem.corp.google.com (hpaq5.eem.corp.google.com [172.25.149.5]) by smtp-out.google.com with ESMTP id o581NWGh007627 for <oauth@ietf.org>; Mon, 7 Jun 2010 18:23:32 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1275960213; bh=to6fynawJpQ3WUoQaAj4KRq3oPw=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type:Content-Transfer-Encoding; b=gSxgN7M9fq+KuQYfAhuem9UFA22GTT+aLdKxdOz3LjxcPLzvHARtaVulexHQaMLk3 ROYqby09NyhI04fR7z6Lw==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:from:date:message-id: subject:to:cc:content-type:content-transfer-encoding; b=To9Ykx4sCznkAhkfw7h9ud5JTHEmwMz2EQGhj7V5xYqxJdTXIKe9v53AeO5ebbt+n k/3G2+gzKwVmTRQPGo/Lg==
Received: from pvc7 (pvc7.prod.google.com [10.241.209.135]) by hpaq5.eem.corp.google.com with ESMTP id o581NTnh016630 for <oauth@ietf.org>; Mon, 7 Jun 2010 18:23:31 -0700
Received: by pvc7 with SMTP id 7so1839000pvc.29 for <oauth@ietf.org>; Mon, 07 Jun 2010 18:23:29 -0700 (PDT)
Received: by 10.141.187.15 with SMTP id o15mr12492511rvp.174.1275960209157; Mon, 07 Jun 2010 18:23:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.141.124.13 with HTTP; Mon, 7 Jun 2010 18:23:09 -0700 (PDT)
In-Reply-To: <C832DD61.6AD3%cmortimore@salesforce.com>
References: <AANLkTil-xDEwMVbV-J7MC1ivoH9w-egOwo5Q2ata94Cc@mail.gmail.com> <C832DD61.6AD3%cmortimore@salesforce.com>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Mon, 07 Jun 2010 18:23:09 -0700
Message-ID: <AANLkTingSGlJNZ5e_stPd1qU5I4gfbh3rQhqYUmqXvdB@mail.gmail.com>
To: Chuck Mortimore <cmortimore@salesforce.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] User-agent flow and pre-registered 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: Tue, 08 Jun 2010 01:23:34 -0000

On Mon, Jun 7, 2010 at 5:31 PM, Chuck Mortimore
<cmortimore@salesforce.com> wrote:
> Note sure I follow this Marius:
>
> “What can happen is that exmple.com/back can pretend to be
> example.com/back, but registration does not help in this case.”
>
> I believe it does help in this case, as the Authorization server can
> validate the registered redirect_uri vs. the requested redirect_uri.   Hence
> the server would not issue a token to exmple.com in this case.   Am I
> missing something?

What stops exmple.com from registering? Unless the authz wants to
operate only with a short list of human verified clients. The current
spec allows that. But if registration cannot be controlled like that,
and all it does it proves that the client owns a domain, then it does
not help.

I don't think registration should/can be enforced.

Marius

v2.23.0 | Report a Bug | By Email