Re: [OAUTH-WG] Alternative Upgrade Flow
Marius Scurtescu <mscurtescu@google.com> Fri, 16 July 2010 16:56 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 1A30B3A67B2 for <oauth@core3.amsl.com>; Fri, 16 Jul 2010 09:56:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.397
X-Spam-Level:
X-Spam-Status: No, score=-105.397 tagged_above=-999 required=5 tests=[AWL=0.580, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, 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 B-uDUG6J2Xrp for <oauth@core3.amsl.com>; Fri, 16 Jul 2010 09:56:27 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 145433A697D for <oauth@ietf.org>; Fri, 16 Jul 2010 09:56:27 -0700 (PDT)
Received: from kpbe15.cbf.corp.google.com (kpbe15.cbf.corp.google.com [172.25.105.79]) by smtp-out.google.com with ESMTP id o6GGuc5K003672 for <oauth@ietf.org>; Fri, 16 Jul 2010 09:56:38 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1279299398; bh=ajyXtdKFTHYsT5tfYcLXvvYoOO0=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=U6mCTFuC5wHyChYOZO6bYlX1VfL8PSx9BYmwKc5EScWDXxxrv08a46r9PCXsZLnuN SNVRuIGPvSHzxO9RGNHWg==
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=C13H/nBRun9p3lf7vpXS4UD8YqdlvP1QAMLXXraMRbYM8EZI3lOZc/Tjo7hSjGyiB UFCUoUyVzFBKK1VIwHwiA==
Received: from yxk8 (yxk8.prod.google.com [10.190.3.136]) by kpbe15.cbf.corp.google.com with ESMTP id o6GGuOYB031065 for <oauth@ietf.org>; Fri, 16 Jul 2010 09:56:37 -0700
Received: by yxk8 with SMTP id 8so599111yxk.16 for <oauth@ietf.org>; Fri, 16 Jul 2010 09:56:37 -0700 (PDT)
Received: by 10.101.171.40 with SMTP id y40mr1631189ano.7.1279299397134; Fri, 16 Jul 2010 09:56:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.93.3 with HTTP; Fri, 16 Jul 2010 09:56:17 -0700 (PDT)
In-Reply-To: <1279298904.11628.74.camel@localhost.localdomain>
References: <1279298904.11628.74.camel@localhost.localdomain>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Fri, 16 Jul 2010 09:56:17 -0700
Message-ID: <AANLkTinkyTjzPVYHqjIXIut17RyLc7Aehuqpv1sgrTtV@mail.gmail.com>
To: Justin Richer <jricher@mitre.org>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Alternative Upgrade 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: Fri, 16 Jul 2010 16:56:29 -0000
On Fri, Jul 16, 2010 at 9:48 AM, Justin Richer <jricher@mitre.org> wrote: > The current proposal for a 1.0->2.0 upgrade flow is to use the assertion > profile and pass the OAuth token in there. Instead, one could create an > endpoint that speaks the 1.0 protocol fully, signatures and client > secrets and everything, but issues 2.0 tokens, JSON and all. It's a > hybridized endpoint also, but put together with the opposite pieces. In > both cases, you put a 1.0 token in one end and get a 2.0 token out the > other. But in this case, the request being made is a completely vanilla > OAuth 1.0 protected resource access request. I already proposed something like that, if there is interest I can update the proposal to be in line with the latest spec: http://www.ietf.org/mail-archive/web/oauth/current/msg02300.html Marius
- [OAUTH-WG] Alternative Upgrade Flow Justin Richer
- Re: [OAUTH-WG] Alternative Upgrade Flow Marius Scurtescu
- Re: [OAUTH-WG] Alternative Upgrade Flow Justin Richer
- Re: [OAUTH-WG] Alternative Upgrade Flow Torsten Lodderstedt
- Re: [OAUTH-WG] Alternative Upgrade Flow Marius Scurtescu
- Re: [OAUTH-WG] Alternative Upgrade Flow William Mills