IETF Logo Mail Archive

Re: [OAUTH-WG] Change grant_type="none" to something less confusing

Eran Hammer-Lahav <eran@hueniverse.com> Fri, 16 July 2010 22:27 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 2425E3A69A5 for <oauth@core3.amsl.com>; Fri, 16 Jul 2010 15:27:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.491
X-Spam-Level:
X-Spam-Status: No, score=-2.491 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599]
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 s5JpfjW-bSbD for <oauth@core3.amsl.com>; Fri, 16 Jul 2010 15:27:05 -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 2B29C3A6862 for <oauth@ietf.org>; Fri, 16 Jul 2010 15:27:05 -0700 (PDT)
Received: (qmail 1791 invoked from network); 16 Jul 2010 22:27:16 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.21) by p3plex1out01.prod.phx3.secureserver.net with SMTP; 16 Jul 2010 22:27:16 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT003.EX1.SECURESERVER.NET ([72.167.180.21]) with mapi; Fri, 16 Jul 2010 15:27:16 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Brian Eaton <beaton@google.com>
Date: Fri, 16 Jul 2010 15:27:03 -0700
Thread-Topic: [OAUTH-WG] Change grant_type="none" to something less confusing
Thread-Index: AcslNgtqPxJK3RFmTOW5ykAWUzOQ/g==
Message-ID: <32537D24-A84A-482C-8B9B-ECA14CB5325C@hueniverse.com>
References: <1279297826.11628.61.camel@localhost.localdomain> <AANLkTinRE0My8GRTVrBM9cwyCWgrpeYQzul3YBp_Z-8A@mail.gmail.com> <5F922BD8-22C9-4E87-9D5B-BAC0529F94C7@hueniverse.com> <AANLkTimAeHyKBAWnia9UU88WvyrFr6GimPrXFEDf_2p1@mail.gmail.com>
In-Reply-To: <AANLkTimAeHyKBAWnia9UU88WvyrFr6GimPrXFEDf_2p1@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Change grant_type="none" to something less confusing
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: Fri, 16 Jul 2010 22:27:06 -0000

The client authentication can be used to retrieve a grant previously arranged. While the grant is linked to the client, it is not always about the client's resources. Calling it 'client' implies it is about the client's resources. 

EHL



On Jul 16, 2010, at 18:19, Brian Eaton <beaton@google.com> wrote:

> On Fri, Jul 16, 2010 at 2:25 PM, Eran Hammer-Lahav <eran@hueniverse.com> wrote:
>> External, out-of-band, implicit.
>> 
>> It cannot be client because that is not always the case.
> 
> Can you point to a use case where someone is going to use the client
> password flow to authenticate something besides a client?
> 
> Because I'm pretty sure that use case is crazy, and can safely be ignored.

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