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

David Recordon <recordond@gmail.com> Fri, 11 June 2010 15:59 UTC

Return-Path: <recordond@gmail.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 538553A695F for <oauth@core3.amsl.com>; Fri, 11 Jun 2010 08:59:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level:
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[AWL=0.588, 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 9fCHTgiZ8pUi for <oauth@core3.amsl.com>; Fri, 11 Jun 2010 08:59:08 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id E77B13A68A3 for <oauth@ietf.org>; Fri, 11 Jun 2010 08:59:07 -0700 (PDT)
Received: by iwn42 with SMTP id 42so1309976iwn.31 for <oauth@ietf.org>; Fri, 11 Jun 2010 08:59:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=SVa5ut9TzLP2e9T89MxcjvVsiKASHP94IMpTz7PMsoI=; b=DHr85nr/hYiWH7CkoT6hDydHnO/Omo1u9azgQHSqTOO+VR3MSSERLyz0wftN8vSJGG AHhVG+8SvLqF6l24Z5UnVaYeug5MaB/6lQhr6Sd0ALWM5Ckyx8eRmXeWQH34gNTZJepu becHrsk+QEPKjfh2Yv/QW/3Xdbl+4egaq9oy0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=wK0/9wNHRUmdcGGtH6j4nYd1M8K928VcDo0H64kDtglLvTuOssxV7eEQ/nsFFeBdbI 04bW8DShv/awCIthg9KaxYAO5Aoof1KhM0U1HhI9VpB5roQ6lB9etdW3OMwJGZIEmKGw k8k5glYTOr9j0E4a2u9lNNDC+ObgbvPQPHpXU=
MIME-Version: 1.0
Received: by 10.231.59.75 with SMTP id k11mr1974569ibh.100.1276271946693; Fri, 11 Jun 2010 08:59:06 -0700 (PDT)
Received: by 10.231.192.4 with HTTP; Fri, 11 Jun 2010 08:59:06 -0700 (PDT)
In-Reply-To: <AANLkTilcpAw7hZuQK43_ybS-wy3bQnPqMfRXOdqY4iYa@mail.gmail.com>
References: <AANLkTingSGlJNZ5e_stPd1qU5I4gfbh3rQhqYUmqXvdB@mail.gmail.com> <C833CEB4.6B81%cmortimore@salesforce.com> <AANLkTinVQEPBVzmiHEGgHhzaILL0nRSvZpjIlrVEJwTw@mail.gmail.com> <AANLkTil1j7vl8PU2tgCzlWY0U6KiWPmRKiVOxvsctB00@mail.gmail.com> <AANLkTimCL-O7RIsUlt_zGDfkEEYb9w4_sPh6zxCMBsf0@mail.gmail.com> <AANLkTin7B9pPgSu3cNlJGkp_gCed-5aPGRZalzXd2Wg8@mail.gmail.com> <4C124A70.2000002@aol.com> <1276268753.31840.50.camel@localhost.localdomain> <4C1257B5.9080706@comlounge.net> <AANLkTilcpAw7hZuQK43_ybS-wy3bQnPqMfRXOdqY4iYa@mail.gmail.com>
Date: Fri, 11 Jun 2010 08:59:06 -0700
Message-ID: <AANLkTimGnTj1HseMsPBaRXjBThM3uktqq0R6P30jsjaZ@mail.gmail.com>
From: David Recordon <recordond@gmail.com>
To: Marius Scurtescu <mscurtescu@google.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: 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: Fri, 11 Jun 2010 15:59:09 -0000

That sounds like a security consideration to me! :)

I imagine that authorization servers will verify ownership in
different manners depending on their tolerance of risk.


On Fri, Jun 11, 2010 at 8:54 AM, Marius Scurtescu <mscurtescu@google.com> wrote:
> On Fri, Jun 11, 2010 at 8:35 AM, Christian Scholz <cs@comlounge.net> wrote:
>> Hi!
>>
>> Am 11.06.10 17:05, schrieb Justin Richer:
>>> Along these lines, I'd like to propose an extension for per-client
>>> instance information to be passed from a client to the server. Things
>>> like a human-readable client name/description, instance name/description
>>> (could be tied to host name, ip, label like "home" or "Work"), and even
>>> something like a display icon. This is especially useful for things like
>>> device clients (where I might have a bunch of devices with the same
>>> client ID) or unregistered clients, where the client id string ends up
>>> being closer to a user-agent string from a browser than a trusted
>>> identifier, especially since it can't have a reliable secret.
>>
>> We have the need for dynamic binding of clients in the User Managed
>> Access group (UMA) as well. I did look into OpenID Connect but felt that
>> reusing an OAuth flow based on a different type is maybe mixing things a
>> bit too much. To me using a flow means that in the end usually
>> you end up with an access token which here is not the case. Especially I
>> don't like the reuse of the token URI as IMHO it's better to use
>> separate endpoints for different APIs.
>>
>> I thus went along and crafted some simple handshake in the UMA
>> specification which I also wanted to move out into a single
>> specification over the next days.
>>
>> You can find it here:
>>
>> http://kantarainitiative.org/confluence/display/~christianscholz/Step+1+experimental+version+v1
>>
>> under "Dynamic binding of OAuth clients".
>>
>> It is a simple handshake where you provide a JSON formatted client
>> descriptor containing the information you describe above and the results
>> is a set of client credentials plus optionally additional information
>> (in UMA we eventually need to pass back more information like additional
>> endpoints).
>
> In general during registration an authz server will verify that the
> client really owns the domain it claims it does. Does any validation
> like that happen in the suggested "Dynamic binding of OAuth clients"?
>
> Marius
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>