Re: [OAUTH-WG] Quick survey: fragment vs. query

Naitik Shah <n@daaku.org> Wed, 14 July 2010 18:48 UTC

Return-Path: <naitiks@gmail.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 BE6333A6A76 for <oauth@core3.amsl.com>; Wed, 14 Jul 2010 11:48:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.976
X-Spam-Level:
X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 vNrB56HDNX7Y for <oauth@core3.amsl.com>; Wed, 14 Jul 2010 11:48:55 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 40EDF3A6A72 for <oauth@ietf.org>; Wed, 14 Jul 2010 11:48:55 -0700 (PDT)
Received: by iwn38 with SMTP id 38so64167iwn.31 for <oauth@ietf.org>; Wed, 14 Jul 2010 11:49:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:sender:received :in-reply-to:references:from:date:x-google-sender-auth:message-id :subject:to:cc:content-type; bh=VXPiiN2TcS+Lh9pl5UCNgNRnny8XiZfSmf2JHNIAOCs=; b=Yb5qwxenMvKcbTkku/5qe1Z91ZJgnnjgxefKR1xu7f8aqm+N3eMynnkEzZEjeb7fmm UHJoriOehYugsR11jWpQbhIth3FbO4p9e++crXFyeLTlDWR5YUTt4HZ9mcS2BD4vOD3s /41KeMlwi8fAyRLxzLPTu+lYLJUcIP8YMU478=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=c8B9I9M8GdGBFtlO0XOQLocDLRi5cePSUYkCes6FJ15d53je+rTvPfdwdiReleZL5v WM8w/djIdsknWIXAN62Suue7O8pGfxAJkpwBLmBRf+3XIqnRL76LJk+IkW/Yji9nBc/A krM+5hVkd/4wi96qnMILzgTcYQeM1ml/+yDdM=
Received: by 10.231.184.168 with SMTP id ck40mr17197843ibb.174.1279133345140; Wed, 14 Jul 2010 11:49:05 -0700 (PDT)
MIME-Version: 1.0
Sender: naitiks@gmail.com
Received: by 10.231.159.193 with HTTP; Wed, 14 Jul 2010 11:48:44 -0700 (PDT)
In-Reply-To: <C862F736.37253%eran@hueniverse.com>
References: <C862F736.37253%eran@hueniverse.com>
From: Naitik Shah <n@daaku.org>
Date: Wed, 14 Jul 2010 11:48:44 -0700
X-Google-Sender-Auth: R1SjFE-upfRxnz5uFBG1JyVVh40
Message-ID: <AANLkTilPKnUUfb44d1gIzLYXWudfZzIklQNAFMcVYKMN@mail.gmail.com>
To: Eran Hammer-Lahav <eran@hueniverse.com>
Content-Type: multipart/alternative; boundary="005045016033a84f3a048b5d70c2"
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Quick survey: fragment vs. query
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: Wed, 14 Jul 2010 18:48:56 -0000

2 and 3 are practically most interesting imho.

(b) is interesting in that if a client application does have SSL, then it's
the simplest flow of all.


-Naitik

On Wed, Jul 14, 2010 at 5:10 AM, Eran Hammer-Lahav <eran@hueniverse.com>wrote:

> Please answer this based on actual use cases. When returning parameters
> using the redirection URI call, which of these combinations make sense?
>
>         | Code | Token | Code & Token
> ---------+------+-------+--------------
> Fragment |  a   |   1   |   3
> Query    |  2   |   b   |   c
> Split*   | n/a  |  n/a  |   d
>
> * token in fragment, code in query
>
> Known use cases:
>
> 1 - current user-agent flow
> 2 - current web-server flow
> 3 - as described by Brian and Naitik
>
> Do you need any of these?
>
> a -
> b -
> c -
> d - current -10 code-and-token proposal
>
> EHL
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>