Re: [OAUTH-WG] OAuth 1 Bridge Flow

Marius Scurtescu <mscurtescu@google.com> Tue, 04 May 2010 18:36 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 1E9B328C19E for <oauth@core3.amsl.com>; Tue, 4 May 2010 11:36:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.653
X-Spam-Level:
X-Spam-Status: No, score=-101.653 tagged_above=-999 required=5 tests=[AWL=0.324, 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 dOS-zD8rqy7s for <oauth@core3.amsl.com>; Tue, 4 May 2010 11:36:20 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id C3A193A6CD4 for <oauth@ietf.org>; Tue, 4 May 2010 11:31:51 -0700 (PDT)
Received: from hpaq5.eem.corp.google.com (hpaq5.eem.corp.google.com [10.3.21.5]) by smtp-out.google.com with ESMTP id o44IVa9t015210 for <oauth@ietf.org>; Tue, 4 May 2010 11:31:36 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1272997897; bh=9tS2RXGlP29S70NePQm96bFqBKA=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=Sj9rzfGub2HZkpZuryzkYAu/TJKBPe6m7fxtVm7u3coHSlm28CaRIwjM3Q/Cf7Htg 7WcgMezyycJR3u5XwQTRA==
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:x-system-of-record; b=QXGwToMu3nKhS0WY7N0ufFCDSMzFB2vKF0fbibQlJmLaN+DuoLOaXm9mCb8glOw7z QFfv3ntcNtx0chKK2lw0Q==
Received: from pzk27 (pzk27.prod.google.com [10.243.19.155]) by hpaq5.eem.corp.google.com with ESMTP id o44IVY3h008924 for <oauth@ietf.org>; Tue, 4 May 2010 11:31:35 -0700
Received: by pzk27 with SMTP id 27so2684461pzk.2 for <oauth@ietf.org>; Tue, 04 May 2010 11:31:34 -0700 (PDT)
Received: by 10.140.83.31 with SMTP id g31mr4932171rvb.3.1272997894152; Tue, 04 May 2010 11:31:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.141.14.15 with HTTP; Tue, 4 May 2010 11:31:14 -0700 (PDT)
In-Reply-To: <AC5DB0CE-9B4D-4D66-936D-E132C8443D89@facebook.com>
References: <AANLkTilxyiK3KXohJJNcY18zv4N3S_pI1WuHOPDI6ctE@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E723439323D0AC6@P3PW5EX1MB01.EX1.SECURESERVER.NET> <AC5DB0CE-9B4D-4D66-936D-E132C8443D89@facebook.com>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Tue, 4 May 2010 11:31:14 -0700
Message-ID: <AANLkTilkVu7yR1DhatXi2-DczIfbbPAq8l32NyC9n70t@mail.gmail.com>
To: Luke Shepard <lshepard@facebook.com>
Content-Type: text/plain; charset=ISO-8859-1
X-System-Of-Record: true
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] OAuth 1 Bridge Flow
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, 04 May 2010 18:36:22 -0000

On Tue, May 4, 2010 at 11:03 AM, Luke Shepard <lshepard@facebook.com> wrote:
> That's a good idea.
>
> FWIW we created a custom endpoint for this purpose - allows you to exchange Facebook sessions for OAuth 2.0 tokens. Documented here: http://developers.facebook.com/docs/guides/upgrade

Thanks for the pointer.

Are the issued OAuth 2.0 access tokens short lived? Is "expires" a
delta or an absolute time?

Marius


>
> On May 4, 2010, at 10:48 AM, Eran Hammer-Lahav wrote:
>
>> Why a short lived 2.0 token? Why not provide an endpoint to exchange a 1.0 token with a 2.0 token with a refresh token?
>>
>> EHL
>>
>>> -----Original Message-----
>>> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf
>>> Of Marius Scurtescu
>>> Sent: Tuesday, May 04, 2010 10:27 AM
>>> To: OAuth WG
>>> Subject: [OAUTH-WG] OAuth 1 Bridge Flow
>>>
>>> Hi,
>>>
>>> I would like to suggest a flow, or endpoint, that is bridging OAuth 1 and
>>> OAuth 2. See the attachment.
>>>
>>> The OAuth 1 Bridge Flow basically defines an endpoint where you can place a
>>> signed OAuth 1 request and in response you receive a short lived OAuth 2.0
>>> access token. This flow can be used by clients that have a long lived OAuth
>>> 1.0 access token and want to use a short lived OAuth 2.0 access token to
>>> access protected resources.
>>>
>>> Do you have a use case for a flow like this? If not exactly but close, how can
>>> the flow be improved to cover your use case as well?
>>>
>>> Feedback more than welcome.
>>>
>>> Thanks,
>>> Marius
>> _______________________________________________
>> OAuth mailing list
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
>
>