Re: [OAUTH-WG] OAuth 1 Bridge Flow

Eran Hammer-Lahav <eran@hueniverse.com> Tue, 04 May 2010 17:49 UTC

Return-Path: <eran@hueniverse.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 13D133A69FA for <oauth@core3.amsl.com>; Tue, 4 May 2010 10:49:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.317
X-Spam-Level:
X-Spam-Status: No, score=-1.317 tagged_above=-999 required=5 tests=[AWL=-1.132, BAYES_40=-0.185]
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 XPe998y7aNFX for <oauth@core3.amsl.com>; Tue, 4 May 2010 10:49:12 -0700 (PDT)
Received: from p3plex1out02.prod.phx3.secureserver.net (p3plex1out02.prod.phx3.secureserver.net [72.167.180.18]) by core3.amsl.com (Postfix) with SMTP id 1337B3A695C for <oauth@ietf.org>; Tue, 4 May 2010 10:49:11 -0700 (PDT)
Received: (qmail 776 invoked from network); 4 May 2010 17:48:54 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.19) by p3plex1out02.prod.phx3.secureserver.net with SMTP; 4 May 2010 17:48:54 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT001.EX1.SECURESERVER.NET ([72.167.180.19]) with mapi; Tue, 4 May 2010 10:48:44 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Marius Scurtescu <mscurtescu@google.com>, OAuth WG <oauth@ietf.org>
Date: Tue, 4 May 2010 10:48:51 -0700
Thread-Topic: [OAUTH-WG] OAuth 1 Bridge Flow
Thread-Index: Acrrr0nZXtEdS8gMSXSO3Rg1yJaqywAArESQ
Message-ID: <90C41DD21FB7C64BB94121FBBC2E723439323D0AC6@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <AANLkTilxyiK3KXohJJNcY18zv4N3S_pI1WuHOPDI6ctE@mail.gmail.com>
In-Reply-To: <AANLkTilxyiK3KXohJJNcY18zv4N3S_pI1WuHOPDI6ctE@mail.gmail.com>
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
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 17:49:13 -0000

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