IETF Logo Mail Archive

Re: [OAUTH-WG] client credentials flow got dropped?

Eran Hammer-Lahav <eran@hueniverse.com> Sun, 11 July 2010 03:16 UTC

Return-Path: <eran@hueniverse.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 BD7473A68BD for <oauth@core3.amsl.com>; Sat, 10 Jul 2010 20:16:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.296
X-Spam-Level:
X-Spam-Status: No, score=-2.296 tagged_above=-999 required=5 tests=[AWL=0.302, BAYES_00=-2.599, 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 EyWc9zO4j0Sx for <oauth@core3.amsl.com>; Sat, 10 Jul 2010 20:16:23 -0700 (PDT)
Received: from p3plex1out01.prod.phx3.secureserver.net (p3plex1out01.prod.phx3.secureserver.net [72.167.180.17]) by core3.amsl.com (Postfix) with SMTP id 42BEE3A68D9 for <oauth@ietf.org>; Sat, 10 Jul 2010 20:16:23 -0700 (PDT)
Received: (qmail 20640 invoked from network); 11 Jul 2010 03:16:29 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.21) by p3plex1out01.prod.phx3.secureserver.net with SMTP; 11 Jul 2010 03:16:29 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT003.EX1.SECURESERVER.NET ([72.167.180.21]) with mapi; Sat, 10 Jul 2010 20:16:29 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Brian Eaton <beaton@google.com>, OAuth WG <oauth@ietf.org>
Date: Sat, 10 Jul 2010 20:16:26 -0700
Thread-Topic: [OAUTH-WG] client credentials flow got dropped?
Thread-Index: AcsgptwKrfNPzVWlTYCDmBCv9GMHPwAAJZLg
Message-ID: <C85E859A.36FAD%eran@hueniverse.com>
In-Reply-To: <AANLkTinVpyyqgU3s3KZx5d_Dk1AYMsBK_U7GX0NgNVPe@mail.gmail.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C85E859A36FADeranhueniversecom_"
MIME-Version: 1.0
Subject: Re: [OAUTH-WG] client credentials flow got dropped?
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: Sun, 11 Jul 2010 03:16:27 -0000

See 'grant_type=none' described in 4.1.

EHL


On 7/10/10 8:12 PM, "Brian Eaton" <beaton@google.com> wrote:

Hi folks -

Draft 6 section 2.9.1 had a section called "Client Requests Access
Token": http://tools.ietf.org/html/draft-ietf-oauth-v2-06#page-34.

In this flow a client presented a client_id and client_secret, and got
an access token in return.

I can't find the corresponding section in draft 7.  It looks like the
rewrite dropped this flow.  Am I missing something?

If this really did get dropped, please add it back.

In terms of normative language, the language in the draft 6 spec was
great.  The only change to that is to drop the refresh token, since it
provides no value.  I've already sent another note about that.

Cheers,
Brian
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

v2.37.1 | Report a Bug | By Email | System Status