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

Torsten Lodderstedt <torsten@lodderstedt.net> Wed, 09 March 2011 20:44 UTC

Return-Path: <torsten@lodderstedt.net>
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 774C83A6AC3 for <oauth@core3.amsl.com>; Wed, 9 Mar 2011 12:44:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.211
X-Spam-Level:
X-Spam-Status: No, score=-2.211 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 mp7jAvm6Kaow for <oauth@core3.amsl.com>; Wed, 9 Mar 2011 12:44:26 -0800 (PST)
Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.31.39]) by core3.amsl.com (Postfix) with ESMTP id A1AEF3A6ABE for <oauth@ietf.org>; Wed, 9 Mar 2011 12:44:25 -0800 (PST)
Received: from [79.253.32.99] (helo=[192.168.71.26]) by smtprelay01.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from <torsten@lodderstedt.net>) id 1PxQGK-0000vh-EJ; Wed, 09 Mar 2011 21:45:40 +0100
Message-ID: <4D77E6F5.2060003@lodderstedt.net>
Date: Wed, 09 Mar 2011 21:45:41 +0100
From: Torsten Lodderstedt <torsten@lodderstedt.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Phil Hunt <phil.hunt@oracle.com>
References: <22FB565B-A701-4502-818F-15164D9E201A@oracle.com>
In-Reply-To: <22FB565B-A701-4502-818F-15164D9E201A@oracle.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Df-Sender: torsten@lodderstedt-online.de
Cc: OAuth WG <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: Wed, 09 Mar 2011 20:44:27 -0000

Hi Phil,

that's great help for anyone looking for advice how to use OAuth.

One remark: In my opinion, the decision process for authorization code 
vs. implicit grant involves more parameters.

refresh token required? --> authz code
client in question is a web application? --> authz code
client in question is a JavaScript app? --> implicit grant
client authentication required --> authz code
else --> implicit grant

regards,
Torsten.

Am 22.02.2011 01:45, schrieb Phil Hunt:
> FYI. I published a blog post with a flow-chart explaining the legs of OAuth.
> http://independentidentity.blogspot.com/2011/02/does-oauth-have-legs.html
>
> Please let me know if any corrections should be made, or for that matter, any improvements!
>
> Phil
> phil.hunt@oracle.com
>
>
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth