IETF Logo Mail Archive

Re: [OAUTH-WG] OAuth 2.0 Mobile WebApp Flow

Eran Hammer-Lahav <eran@hueniverse.com> Fri, 11 June 2010 21:57 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 CDF7E3A6783 for <oauth@core3.amsl.com>; Fri, 11 Jun 2010 14:57:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.027
X-Spam-Level:
X-Spam-Status: No, score=-2.027 tagged_above=-999 required=5 tests=[AWL=0.571, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 M+ubjWT4Qa0O for <oauth@core3.amsl.com>; Fri, 11 Jun 2010 14:57:23 -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 B504F3A697D for <oauth@ietf.org>; Fri, 11 Jun 2010 14:57:23 -0700 (PDT)
Received: (qmail 14935 invoked from network); 11 Jun 2010 21:57:25 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.20) by p3plex1out02.prod.phx3.secureserver.net with SMTP; 11 Jun 2010 21:57:25 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT002.EX1.SECURESERVER.NET ([72.167.180.20]) with mapi; Fri, 11 Jun 2010 14:57:26 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Nat Sakimura <sakimura@gmail.com>, James Manger <James.H.Manger@team.telstra.com>
Date: Fri, 11 Jun 2010 14:57:22 -0700
Thread-Topic: [OAUTH-WG] OAuth 2.0 Mobile WebApp Flow
Thread-Index: AcsGw8pgn3wY4yWjRDWz+Stub3TdcgC7UdDs
Message-ID: <C837FF52.358CC%eran@hueniverse.com>
In-Reply-To: <AANLkTimIXMReEaB3ShbZIjWjiBH-VUjrvHgKHCzgVOu0@mail.gmail.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C837FF52358CCeranhueniversecom_"
MIME-Version: 1.0
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] OAuth 2.0 Mobile WebApp 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, 11 Jun 2010 21:57:27 -0000

I'd still like to see this proposed as a new I-D. It can be very short. I will have the extensibility guidelines in the next draft or two, but you can start by just declaring a new parameter for the relevant endpoints.

EHL


On 6/7/10 7:53 PM, "Nat Sakimura" <sakimura@gmail.com> wrote:

I fully agree on it.

Instead of doing as a flow, defining request_url as one of the core variable would be better.
The question then is, whether this community accepts the idea.

On Mon, Jun 7, 2010 at 10:51 PM, Manger, James H <James.H.Manger@team.telstra.com> wrote:
Nat,

> On the other hand, you are starting to think of it as a generic "include" mechanism, are you?

Yes. That feels like the simplest mental model for this functionality, and the simplest way to specify it.

--
James Manger

v2.46.0 | Report a Bug | By Email | System Status