Re: [OAUTH-WG] Native Client Extension

"Richer, Justin P." <jricher@mitre.org> Thu, 27 January 2011 19:38 UTC

Return-Path: <jricher@mitre.org>
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 A06ED28C179 for <oauth@core3.amsl.com>; Thu, 27 Jan 2011 11:38:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.361
X-Spam-Level:
X-Spam-Status: No, score=-4.361 tagged_above=-999 required=5 tests=[AWL=0.238, BAYES_00=-2.599, GB_I_LETTER=-2]
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 NKr678jByKf1 for <oauth@core3.amsl.com>; Thu, 27 Jan 2011 11:38:38 -0800 (PST)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by core3.amsl.com (Postfix) with ESMTP id B711F28C178 for <oauth@ietf.org>; Thu, 27 Jan 2011 11:38:38 -0800 (PST)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 9AE4721B070E; Thu, 27 Jan 2011 14:41:42 -0500 (EST)
Received: from imchub2.MITRE.ORG (imchub2.mitre.org [129.83.29.74]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 93A1021B0E2C; Thu, 27 Jan 2011 14:41:42 -0500 (EST)
Received: from IMCMBX3.MITRE.ORG ([129.83.29.206]) by imchub2.MITRE.ORG ([129.83.29.74]) with mapi; Thu, 27 Jan 2011 14:41:42 -0500
From: "Richer, Justin P." <jricher@mitre.org>
To: Skylar Woodward <skylar@kiva.org>, Marius Scurtescu <mscurtescu@google.com>
Date: Thu, 27 Jan 2011 14:39:54 -0500
Thread-Topic: [OAUTH-WG] Native Client Extension
Thread-Index: Acu+EWaVnDOBczSKTMSP/6qN/u5OfQASJH7+
Message-ID: <D24C564ACEAD16459EF2526E1D7D605D0FFC3C713D@IMCMBX3.MITRE.ORG>
References: <AANLkTi=YWLHV1Yi0bdKTaDaBw3X5D6Y_kk3xt7EvJHe_@mail.gmail.com> <4D239DCF.4030501@lodderstedt.net> <AANLkTi=RAS5X0jUjxFzf6k1_r+79NFSFjmZs2bw2Lg3o@mail.gmail.com>, <3C83928E-56D5-4386-A075-9ECF1F3A469C@kiva.org>
In-Reply-To: <3C83928E-56D5-4386-A075-9ECF1F3A469C@kiva.org>
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
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Native Client Extension
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: Thu, 27 Jan 2011 19:38:39 -0000

+1 on out of band auth being moved to a more fully-specified extension. It can (and likely should) still use mechanisms such as auth codes, but with different requirements such as no return URL. This is where things like the <title>code</title> hack can live, as well.

 -- Justin
________________________________________
From: oauth-bounces@ietf.org [oauth-bounces@ietf.org] On Behalf Of Skylar Woodward [skylar@kiva.org]
Sent: Thursday, January 27, 2011 6:00 AM
To: Marius Scurtescu
Cc: OAuth WG
Subject: Re: [OAUTH-WG] Native Client Extension

Marius,

I support the extension (as per my previous letter, as I missed this thread over the holidays) and Kiva is/was planning to support this as well.  Given the unpredictable technology environments of many of our customers, this flow is essential for our implementation.

However, now reviewing language in draft-12, I wonder if it isn't more clear to define the extension as using a different response_type (eg, oob_code).  In the past, the use of "oob" has been more of hack to work with existing specs. In truth, it is a unique flow of its own compared to Implict and Auth Code as they are currently defined.  Such a flow would not accept a redirect_url and could use "oob_code" for both response_type and grant_type.

skylar


On Jan 4, 2011, at 11:58 PM, Marius Scurtescu wrote:

> On Tue, Jan 4, 2011 at 2:23 PM, Torsten Lodderstedt
> <torsten@lodderstedt.net> wrote:
>> +1
>>
>> I have asked myself all the time why "oob" disappeared in OAuth 2.0? Does
>> Google use this feature?
>
> Yes, we are planning to support this, exactly as described in the extension.
>
> Marius
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth