IETF Logo Mail Archive

Re: [OAUTH-WG] native app support (was: Next draft)

Marius Scurtescu <mscurtescu@google.com> Tue, 22 June 2010 20:02 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 E18773A69E6 for <oauth@core3.amsl.com>; Tue, 22 Jun 2010 13:02:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.73
X-Spam-Level:
X-Spam-Status: No, score=-100.73 tagged_above=-999 required=5 tests=[AWL=-0.242, BAYES_05=-1.11, FM_FORGED_GMAIL=0.622, 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 oZT0zfhsx3pA for <oauth@core3.amsl.com>; Tue, 22 Jun 2010 13:02:37 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id DFDA43A6858 for <oauth@ietf.org>; Tue, 22 Jun 2010 13:02:36 -0700 (PDT)
Received: from wpaz5.hot.corp.google.com (wpaz5.hot.corp.google.com [172.24.198.69]) by smtp-out.google.com with ESMTP id o5MK2gbq017841 for <oauth@ietf.org>; Tue, 22 Jun 2010 13:02:43 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1277236963; bh=xoabgFtRCR70xtp0/66YCvakwMY=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=oQmaDQRQFS51s4u/SwQHnGWk1vl68tc+XYZBIwY0B+HxhA1xNusB93Qo9XHHajMss HspA+0XSCrNK2bQEbVMQw==
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=odSKer+/L5WAae84aLRm+1cIi6HbKE5U+4c9VQPKiTUXjjYtDUjWf06EegPw1TCjU A7Zef/sA7EDLko62m62Kw==
Received: from gxk8 (gxk8.prod.google.com [10.202.11.8]) by wpaz5.hot.corp.google.com with ESMTP id o5MK2fWl025557 for <oauth@ietf.org>; Tue, 22 Jun 2010 13:02:41 -0700
Received: by gxk8 with SMTP id 8so437276gxk.31 for <oauth@ietf.org>; Tue, 22 Jun 2010 13:02:41 -0700 (PDT)
Received: by 10.101.73.11 with SMTP id a11mr5538317anl.130.1277236961119; Tue, 22 Jun 2010 13:02:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.101.132.22 with HTTP; Tue, 22 Jun 2010 13:02:21 -0700 (PDT)
In-Reply-To: <AANLkTikkG3T_DYKhjMbyYayi7SzZel3RJXFSguxq7SSZ@mail.gmail.com>
References: <AANLkTikkG3T_DYKhjMbyYayi7SzZel3RJXFSguxq7SSZ@mail.gmail.com>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Tue, 22 Jun 2010 13:02:21 -0700
Message-ID: <AANLkTilycD2urJZqbP8HaRcqUQ6bM30WAzy4c4VOmLql@mail.gmail.com>
To: Eran Hammer-Lahav <eran@hueniverse.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: "OAuth WG (oauth@ietf.org)" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] native app support (was: Next draft)
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, 22 Jun 2010 20:02:38 -0000

On Tue, Jun 8, 2010 at 10:46 AM, Marius Scurtescu <mscurtescu@google.com> wrote:
> In order to properly support native applications I suggest the
> following changes:
> [...]
> 2. optional redirect_uri (default result page)
>
> Some native apps do not have a redirect_uri, as a result two things are needed:
>
> 2.1 Either make redirect_uri optional or define a standard value that
> signals that the client does not have such a page.
>
> 2.2 The authz server must supply a default result page, if there is no
> redirect_uri. Also, this page should put the verification code and the
> client state (code and state) in the page title in a standard way such
> that the native app can extract them from the window title. WRAP
> defined how the title should be formed.

Should this also go to an extension? It is not introducing any new
parameters, not sure if it belongs there. OAuth 1 at least defined the
"oob" special value.

Marius

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