IETF Logo Mail Archive

Re: [OAUTH-WG] Flowchart for legs of OAuth

Marius Scurtescu <mscurtescu@google.com> Mon, 04 April 2011 18:28 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 7B7DD3A6405 for <oauth@core3.amsl.com>; Mon, 4 Apr 2011 11:28:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.921
X-Spam-Level:
X-Spam-Status: No, score=-105.921 tagged_above=-999 required=5 tests=[AWL=0.056, 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 cpnDzBazlbJB for <oauth@core3.amsl.com>; Mon, 4 Apr 2011 11:28:38 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 2BEB13A63D2 for <oauth@ietf.org>; Mon, 4 Apr 2011 11:28:38 -0700 (PDT)
Received: from hpaq14.eem.corp.google.com (hpaq14.eem.corp.google.com [172.25.149.14]) by smtp-out.google.com with ESMTP id p34IUJTv001159 for <oauth@ietf.org>; Mon, 4 Apr 2011 11:30:20 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1301941820; bh=HDowctoAyYiGegOdSYRr2p4VyFk=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=Xa+0LNnm0LWYKd4i+eE3LdjauyxTvto+t4vEgdIq8mPRJDZ5U0lbRx0y6k860IcVN VBcmexvUzO8eczDiz1Efg==
Received: from ywg8 (ywg8.prod.google.com [10.192.7.8]) by hpaq14.eem.corp.google.com with ESMTP id p34ITHh6006119 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <oauth@ietf.org>; Mon, 4 Apr 2011 11:30:18 -0700
Received: by ywg8 with SMTP id 8so3369347ywg.20 for <oauth@ietf.org>; Mon, 04 Apr 2011 11:30:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=Jb7Nq3qIJMgOrDBShAE7MZ+d0x1hGt5wTMFBeIujLls=; b=UYoyb9k1yfMmyH3EmVROh+BaQj/hztASmHvoVB1k56qrGq9UVovVbNxKKoXMA1aSwO N4nounb91M/SrBXotbkw==
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; b=hL02pCjeQUzjk8mfyf/UMCvyAcpuKn0G5kvGDoTYpRbTEWQLJ2cMUvekL902W49P3K XQnf5JWUW0jM2oc43rww==
Received: by 10.101.65.13 with SMTP id s13mr5367624ank.148.1301941818124; Mon, 04 Apr 2011 11:30:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.34.4 with HTTP; Mon, 4 Apr 2011 11:29:58 -0700 (PDT)
In-Reply-To: <65E3F250-5111-4692-BFA7-F5B838E9B41D@gmail.com>
References: <22FB565B-A701-4502-818F-15164D9E201A@oracle.com> <AANLkTimGjiCGk5dpA=YVzq5vDkLR2+caSz=pZ5WiZO9H@mail.gmail.com> <3C84AD7A-F00F-43EC-AAD3-AD2DCFB46B0E@oracle.com> <90C41DD21FB7C64BB94121FBBC2E7234464F432BB0@P3PW5EX1MB01.EX1.SECURESERVER.NET> <4D84F7E2.6090305@redhat.com> <16B9A882-6204-4CBD-B7E3-1D806AF5056C@oracle.com> <4D8A5054.4050006@lodderstedt.net> <BANLkTiniuuRXtkzLubgOjVursVtOGjFe6A@mail.gmail.com> <7616C235-2913-4EE0-A710-F47A4CC9E424@oracle.com> <BANLkTi=XyF25vB6qKX2q8iOpEaZ1yQx9Jw@mail.gmail.com> <65E3F250-5111-4692-BFA7-F5B838E9B41D@gmail.com>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Mon, 04 Apr 2011 11:29:58 -0700
Message-ID: <BANLkTik5u5+jjTwnwNCQVyzMux4aMB98yg@mail.gmail.com>
To: Kris Selden <kris.selden@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] Flowchart for legs of OAuth
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: Mon, 04 Apr 2011 18:28:39 -0000

On Mon, Apr 4, 2011 at 10:47 AM, Kris Selden <kris.selden@gmail.com> wrote:
> A typical iPhone app cannot be shipped with a client secret and rightly or wrongly users expect to only have to enter their credentials once.
>
> What is the best profile to use for an app that can't have a client secret and needs a refresh token or a long lived access token?

The authorization code grant, aka web server flow.

The spec is misleading in this respect IMO.

Marius

v2.23.0 | Report a Bug | By Email