Re: [OAUTH-WG] OAuth 1.0 token assertion to OAuth 2.0 token (was: Draft -09)

Marius Scurtescu <mscurtescu@google.com> Wed, 30 June 2010 01:50 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 864523A68D4 for <oauth@core3.amsl.com>; Tue, 29 Jun 2010 18:50:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.488
X-Spam-Level:
X-Spam-Status: No, score=-101.488 tagged_above=-999 required=5 tests=[AWL=0.489, 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 d3B9g38Vz1-Z for <oauth@core3.amsl.com>; Tue, 29 Jun 2010 18:50:24 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id 6BF783A6844 for <oauth@ietf.org>; Tue, 29 Jun 2010 18:50:24 -0700 (PDT)
Received: from wpaz33.hot.corp.google.com (wpaz33.hot.corp.google.com [172.24.198.97]) by smtp-out.google.com with ESMTP id o5U1oY5w008159 for <oauth@ietf.org>; Tue, 29 Jun 2010 18:50:34 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1277862634; bh=CKAyIcOjA9UDTLydDdEAHlHP/Y4=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type:Content-Transfer-Encoding; b=Kq5zlUp2j+gvQ2FHW0oLz0BGaLOseUFb07C1VsPm8pPceKrH0MjQDdCgR6XJ3yn9N QR7rQmFKWKSsKMIQnfx5A==
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:x-system-of-record; b=pA39UMoVIWk6Vr8Lhfsvt+oqfl+4UZKtfhjMxs03y143r94tF77PYAh4sw8M/UHVO 1AXzerBGCae1attN+bCSw==
Received: from vws13 (vws13.prod.google.com [10.241.21.141]) by wpaz33.hot.corp.google.com with ESMTP id o5U1oWGG009952 for <oauth@ietf.org>; Tue, 29 Jun 2010 18:50:33 -0700
Received: by vws13 with SMTP id 13so505985vws.27 for <oauth@ietf.org>; Tue, 29 Jun 2010 18:50:32 -0700 (PDT)
Received: by 10.220.126.197 with SMTP id d5mr4317201vcs.29.1277862632405; Tue, 29 Jun 2010 18:50:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.83.100 with HTTP; Tue, 29 Jun 2010 18:50:12 -0700 (PDT)
In-Reply-To: <1B9AF9A1-697C-4C21-A8A2-0D94B90EB599@facebook.com>
References: <AANLkTikMuFIaJ1bnL3FOSzsRmO0Ix9xzyyzQG0hcWVcV@mail.gmail.com> <1B9AF9A1-697C-4C21-A8A2-0D94B90EB599@facebook.com>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Tue, 29 Jun 2010 18:50:12 -0700
Message-ID: <AANLkTiklDiFsOyponWyRdPVZoKGL4zPV5KJt9txW-gqL@mail.gmail.com>
To: Luke Shepard <lshepard@facebook.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)" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] OAuth 1.0 token assertion to OAuth 2.0 token (was: Draft -09)
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: Wed, 30 Jun 2010 01:50:27 -0000

On Tue, Jun 29, 2010 at 6:30 PM, Luke Shepard <lshepard@facebook.com> wrote:
> One reason is that you may want to exchange tokens in a batch, whereas you typically can only sign requests individually.

How does the assertion grant type help in this case? As far as I can
tell this also allows you to exchange only one token.

Marius


>
> On Jun 29, 2010, at 6:12 PM, Marius Scurtescu wrote:
>
>> On Tue, Jun 29, 2010 at 8:22 AM, Eran Hammer-Lahav <eran@hueniverse.com> wrote:
>>>
>>> The assertion grant type is really the grant type extension point. Libraries should treat it as a way to support custom grant types. One of the things I would like to see someone draft is how to use OAuth 1.0 tokens to obtain OAuth 2.0 tokens using the assertion type. For example, the assertion type can be "http://oauth.net/1.0/token" , and the assertion itself is some form of the token and signature (or secrets) concatenated into a string (this will maintain the 1.0 security while transitioning to 2.0). This is just a straw man.
>>>
>>> It is important that libraries support this extensibility with some form of a hook or handler so that clients can make requests using assertions from outside the library.
>>
>> An OAuth 1 token assertion as described above would achieve the same
>> thing as the suggested bridge endpoint. Do you see any advantages on
>> using an assertion as opposed to a standard OAuth 1 signed request?
>>
>> Marius
>> _______________________________________________
>> OAuth mailing list
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
>
>