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

Brian Eaton <beaton@google.com> Mon, 19 July 2010 21:31 UTC

Return-Path: <beaton@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 EA5F53A6B7A for <oauth@core3.amsl.com>; Mon, 19 Jul 2010 14:31:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.83
X-Spam-Level:
X-Spam-Status: No, score=-105.83 tagged_above=-999 required=5 tests=[AWL=0.147, 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 4ZFt1g7yFPWr for <oauth@core3.amsl.com>; Mon, 19 Jul 2010 14:31:01 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 1A7C43A6B85 for <oauth@ietf.org>; Mon, 19 Jul 2010 14:30:52 -0700 (PDT)
Received: from hpaq5.eem.corp.google.com (hpaq5.eem.corp.google.com [172.25.149.5]) by smtp-out.google.com with ESMTP id o6JLUt2O006402 for <oauth@ietf.org>; Mon, 19 Jul 2010 14:30:56 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1279575056; bh=3napwc2+42nuquwMcBZGu7h9cBE=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type:Content-Transfer-Encoding; b=ucucH6ZTZcFe3UXdK9Jg35w/4uoO0rHU9qa8EqmLN3+UpnUfEAi/lBY3HW7l558T8 /uury5zEuoKBgxWB2QZTA==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:content-transfer-encoding:x-system-of-record; b=aQr/2DSSLp8nrRWQr0xkQkGo4DidLRt5WfJmKeQtu689FH2xww6ra+DDh5E1RjGzy 0wKmHUJtMduR3tQn39bjQ==
Received: from pxi11 (pxi11.prod.google.com [10.243.27.11]) by hpaq5.eem.corp.google.com with ESMTP id o6JLUrYJ008494 for <oauth@ietf.org>; Mon, 19 Jul 2010 14:30:54 -0700
Received: by pxi11 with SMTP id 11so2467354pxi.21 for <oauth@ietf.org>; Mon, 19 Jul 2010 14:30:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.177.21 with SMTP id z21mr1778666wfe.160.1279575043608; Mon, 19 Jul 2010 14:30:43 -0700 (PDT)
Received: by 10.143.132.1 with HTTP; Mon, 19 Jul 2010 14:30:43 -0700 (PDT)
In-Reply-To: <1279559831.6181.17.camel@localhost.localdomain>
References: <1279297826.11628.61.camel@localhost.localdomain> <AANLkTinRE0My8GRTVrBM9cwyCWgrpeYQzul3YBp_Z-8A@mail.gmail.com> <AANLkTim_GpxKx2G6FQN9TGwMYxnRv4N7pOo7Yo3g2s6c@mail.gmail.com> <AANLkTinDwGDYq4IYA9BKJakdEMnR8FbruTqR4i_zS88p@mail.gmail.com> <AANLkTinbbIJ03UPFWibPJC569ckseU33Tnyf-1BYRGj2@mail.gmail.com> <AANLkTimfdpugQSgTMUPtLy-xOMIB-dJ4E8IMzB5EwU6R@mail.gmail.com> <AANLkTintmqhY1PY51h4DcXEI0r3FQmIB92pP3vykPQrw@mail.gmail.com> <3AF1FD6F-2178-42ED-833C-D93C534DDA8A@hueniverse.com> <AANLkTindn2UOcqWz410_UnyAORe58_XpXQKcy5sMt_pF@mail.gmail.com> <AA83846D-1817-4B51-9F3E-CA9DD91862D6@facebook.com> <AANLkTinrz-KCjHpeUCnDpJhRGRCHoY_nl3fKgNgivoxi@mail.gmail.com> <81CECB0D-6AFE-4E21-9211-86648FC6EAA8@hueniverse.com> <1279559831.6181.17.camel@localhost.localdomain>
Date: Mon, 19 Jul 2010 14:30:43 -0700
Message-ID: <AANLkTiliwXhXDmhW2Va_VZ_LPlPj0Ryg12QzHPtH7xCP@mail.gmail.com>
From: Brian Eaton <beaton@google.com>
To: Justin Richer <jricher@mitre.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
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: Mon, 19 Jul 2010 21:31:03 -0000

client credentials works for me as well.

On Mon, Jul 19, 2010 at 10:17 AM, Justin Richer <jricher@mitre.org> wrote:
> "client_credentials" is fine with me for the name of this grant type.
> I'd also like the paragraph describing its use to be pulled out into a
> subsection, to be parallel with all the other grant types.
>
>  -- Justin
>
> On Sat, 2010-07-17 at 15:51 -0400, Eran Hammer-Lahav wrote:
>> client_credentials worked fine before. I'll just replace none with that. No one had an issue with the name in -05.
>>
>> EHL
>>
>>
>>
>> On Jul 17, 2010, at 15:49, Brian Eaton <beaton@google.com> wrote:
>>
>> > On Sat, Jul 17, 2010 at 8:52 AM, Luke Shepard <lshepard@facebook.com> wrote:
>> >> As far as consistency, it is just a little weird to call it "client password" in one
>> >> part of the spec, when it's defined as "client secret" elsewhere.
>> >
>> > Agreed, we could be more consistent.  The value we're talking about is
>> > the same in all of the flows, no sense in switching terminology.
>> >
>> > I prefer client_password, because "password", for me, evokes all the
>> > right kinds of security concerns.  Password storage, encryption on the
>> > wire, etc...
>> >
>> > I'm less happy with client_secret, though I can certainly live with
>> > it.  My main concern with client_secret is that people might confuse
>> > it with a signing secret.  The value is not used for signing.  If we
>> > are going to have flows where clients have secrets that are used for
>> > cryptographic authentication, then I would want to call those "keys"
>> > instead.
>> >
>> >> How about just "client_only" ?
>> >
>> > That would be fine by me.
>> _______________________________________________
>> OAuth mailing list
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
>
>
>