IETF Logo Mail Archive

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

Marius Scurtescu <mscurtescu@google.com> Thu, 31 March 2011 23:40 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 800D13A6AC9 for <oauth@core3.amsl.com>; Thu, 31 Mar 2011 16:40:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.977
X-Spam-Level:
X-Spam-Status: No, score=-105.977 tagged_above=-999 required=5 tests=[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 P0GytpVFo+JL for <oauth@core3.amsl.com>; Thu, 31 Mar 2011 16:40:31 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 9ACA93A69BE for <oauth@ietf.org>; Thu, 31 Mar 2011 16:40:31 -0700 (PDT)
Received: from kpbe20.cbf.corp.google.com (kpbe20.cbf.corp.google.com [172.25.105.84]) by smtp-out.google.com with ESMTP id p2VNgAjo026239 for <oauth@ietf.org>; Thu, 31 Mar 2011 16:42:10 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1301614931; bh=ko4zY+3enX4BZAqhOhNHO+DnkHU=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=Zmtkdx2XcIuhSTnL8bk2YSmaDZklE+rDCe240fZyfVho3JV1T8djBAhxT5La45q7H 8+eazWOczoJUQMyxuLOHQ==
Received: from gyg8 (gyg8.prod.google.com [10.243.50.136]) by kpbe20.cbf.corp.google.com with ESMTP id p2VNfpRK002180 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <oauth@ietf.org>; Thu, 31 Mar 2011 16:42:09 -0700
Received: by gyg8 with SMTP id 8so1310635gyg.38 for <oauth@ietf.org>; Thu, 31 Mar 2011 16:42:09 -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=ldqcgBKoCYD1YTtP4mboMcpuPA8cBrgykxsmWd1YYD8=; b=ntDg+81AkjL/AG9fuz3fHX+9apgVo5VBry12Rs3pn11P2fCYhD9u87Lgh1HY0vYpfO 3iahRs8czMhjMQth5Cig==
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=LNA9BVYgisMrJTXQ97AoSBQSvsBc6A9Ax5JCFUm+RG9NX+F9rHVfjnFGaU4DrKrMDf hC4vQPfGCDmmpk1+wwhA==
Received: by 10.101.83.11 with SMTP id k11mr2502426anl.38.1301614929153; Thu, 31 Mar 2011 16:42:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.34.4 with HTTP; Thu, 31 Mar 2011 16:41:49 -0700 (PDT)
In-Reply-To: <4D8A5054.4050006@lodderstedt.net>
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>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Thu, 31 Mar 2011 16:41:49 -0700
Message-ID: <BANLkTiniuuRXtkzLubgOjVursVtOGjFe6A@mail.gmail.com>
To: Torsten Lodderstedt <torsten@lodderstedt.net>
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: Thu, 31 Mar 2011 23:40:32 -0000

On Wed, Mar 23, 2011 at 12:56 PM, Torsten Lodderstedt
<torsten@lodderstedt.net> wrote:
> Hi Phil,
>
> looks even better now :-)
>
> As already pointed out
> (http://www.ietf.org/mail-archive/web/oauth/current/msg05599.html), "Have
> client credentials? No" does not automatically imply usage of implicit
> grant. The client could also use the authorization code (for various
> reasons).

+1, no client credentials does not necessarily imply the implicit grant.

Marius

v2.23.0 | Report a Bug | By Email