IETF Logo Mail Archive

Re: [OAUTH-WG] User-Agent flow and refresh tokens

Marius Scurtescu <mscurtescu@google.com> Thu, 16 September 2010 19:35 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 541643A68EB for <oauth@core3.amsl.com>; Thu, 16 Sep 2010 12:35:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.77
X-Spam-Level:
X-Spam-Status: No, score=-105.77 tagged_above=-999 required=5 tests=[AWL=0.207, 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 FaR0baHzbm+n for <oauth@core3.amsl.com>; Thu, 16 Sep 2010 12:35:56 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 1DDC53A682D for <oauth@ietf.org>; Thu, 16 Sep 2010 12:35:56 -0700 (PDT)
Received: from hpaq5.eem.corp.google.com (hpaq5.eem.corp.google.com [172.25.149.5]) by smtp-out.google.com with ESMTP id o8GJaKKN004622 for <oauth@ietf.org>; Thu, 16 Sep 2010 12:36:20 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1284665780; bh=MVzdYJNykooSdEb8bL3BkPiMq2U=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type:Content-Transfer-Encoding; b=OKFrSn/MKn9RVIAOkbA/sH9bxk1o0+Mmvf74sTolSy/UIC2DYqkjPKkFlyICOWRnu qtE40ptomRlsXV0nYYEYA==
Received: from gxk4 (gxk4.prod.google.com [10.202.11.4]) by hpaq5.eem.corp.google.com with ESMTP id o8GJaI6G028818 for <oauth@ietf.org>; Thu, 16 Sep 2010 12:36:19 -0700
Received: by gxk4 with SMTP id 4so858508gxk.25 for <oauth@ietf.org>; Thu, 16 Sep 2010 12:36:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=s/GN4GPGs82MMDC+Urdejr2a3vanb1bN6N0OiTUNFc0=; b=iyTVPHKE3dplSO8QBbi2LTbOZrP4MU5527wP4qGa9C+u4CVBV8AVnUYeCkl/mKRwOC IhxsbuDIyCUEJdU8Kybg==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=dY8aQ/zvtMUGxQy9zFwYb6+v/mjS7Zd0s0nIlJmoTtnXam15Slyo+Cq2BgrxIvJf+q e7dBywZnTqtvKq6fRZLA==
Received: by 10.101.201.9 with SMTP id d9mr4083094anq.263.1284665778174; Thu, 16 Sep 2010 12:36:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.6.6 with HTTP; Thu, 16 Sep 2010 12:35:57 -0700 (PDT)
In-Reply-To: <6A068F15-5B15-444E-AAC3-354EFB866A4A@lodderstedt.net>
References: <4C913EE3.90704@lodderstedt.net> <AANLkTikJGDUKCfiPiN_rAVXmbPF0SBN_sKNQFHw6-oqj@mail.gmail.com> <AANLkTime0dayBq1k+ee7xNp3pkBE2-Ltn-i=LNh0-XvB@mail.gmail.com> <0B18D334-441B-48C0-8836-8F285404B53F@lodderstedt.net> <AANLkTimL1TL57iJ5MOJTcEmog5e-9vjZNCOAyKLS4Dt1@mail.gmail.com> <6A068F15-5B15-444E-AAC3-354EFB866A4A@lodderstedt.net>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Thu, 16 Sep 2010 12:35:57 -0700
Message-ID: <AANLkTi=KpHx0+k+Lu=0ykDVYUpvd2cWmbBFMeRMwp2uj@mail.gmail.com>
To: Torsten Lodderstedt <torsten@lodderstedt.net>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
Cc: "OAuth WG (oauth@ietf.org)" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] User-Agent flow and refresh tokens
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, 16 Sep 2010 19:35:58 -0000

On Thu, Sep 16, 2010 at 12:00 PM, Torsten Lodderstedt
<torsten@lodderstedt.net> wrote:
> I don't know whether I understand you correctly. Are you saying that refresh tokens only make sense in Web servers?

I was referring to the "web server" flow/profile. Not web servers in general.

Why would a native app use the user-agent flow (response_type=token)
over the web server flow (response_type=code)?

Marius

>
> regards,
> Torsten.
>
>
>
> Am 16.09.2010 um 18:04 schrieb Marius Scurtescu <mscurtescu@google.com>:
>
>> On Wed, Sep 15, 2010 at 10:39 PM, Torsten Lodderstedt
>> <torsten@lodderstedt.net> wrote:
>>> Am 16.09.2010 um 05:53 schrieb Andrew Arnott <andrewarnott@gmail.com>:
>>>
>>> The user agent flow works for native apps that can host a web browser.  It
>>> works pretty well in my experience.
>>>
>>> Would like to see support for refresh tokens in this flow?
>>
>> Sure, User-Agent works for native apps, but why would you use this
>> flow over web server?
>>
>> In other words, why add refresh tokens to user-agent when you can use
>> web server?
>>
>> Thanks,
>> Marius
>

v2.23.0 | Report a Bug | By Email