Re: [OAUTH-WG] OAuth 1 Bridge Flow

Luke Shepard <lshepard@facebook.com> Tue, 04 May 2010 18:05 UTC

Return-Path: <lshepard@facebook.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 D2B063A697C for <oauth@core3.amsl.com>; Tue, 4 May 2010 11:05:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.269
X-Spam-Level:
X-Spam-Status: No, score=-2.269 tagged_above=-999 required=5 tests=[AWL=-0.493, BAYES_05=-1.11, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1]
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 Z6eWuC0nbV60 for <oauth@core3.amsl.com>; Tue, 4 May 2010 11:05:27 -0700 (PDT)
Received: from mailout-snc1.facebook.com (mailout-snc1.facebook.com [69.63.179.25]) by core3.amsl.com (Postfix) with ESMTP id BE5AD3A67AF for <oauth@ietf.org>; Tue, 4 May 2010 11:05:27 -0700 (PDT)
Received: from mail.thefacebook.com ([192.168.18.105]) by pp01.snc1.tfbnw.net (8.14.3/8.14.3) with ESMTP id o44I3WPQ008896 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 4 May 2010 11:03:43 -0700
Received: from SC-MBXC1.TheFacebook.com ([192.168.18.102]) by sc-hub02.TheFacebook.com ([192.168.18.105]) with mapi; Tue, 4 May 2010 11:03:14 -0700
From: Luke Shepard <lshepard@facebook.com>
To: Eran Hammer-Lahav <eran@hueniverse.com>
Date: Tue, 4 May 2010 11:03:12 -0700
Thread-Topic: [OAUTH-WG] OAuth 1 Bridge Flow
Thread-Index: AcrrtBB0w/60YWjYS+ms+0tkfmlr0w==
Message-ID: <AC5DB0CE-9B4D-4D66-936D-E132C8443D89@facebook.com>
References: <AANLkTilxyiK3KXohJJNcY18zv4N3S_pI1WuHOPDI6ctE@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E723439323D0AC6@P3PW5EX1MB01.EX1.SECURESERVER.NET>
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E723439323D0AC6@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5, 1.2.40, 4.0.166 definitions=2010-05-04_05:2010-02-06, 2010-05-04, 2010-05-03 signatures=0
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:05:28 -0000

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

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