IETF Logo Mail Archive

Re: [OAUTH-WG] treatment of client_id for authentication and identification

Torsten Lodderstedt <torsten@lodderstedt.net> Wed, 27 July 2011 22:21 UTC

Return-Path: <torsten@lodderstedt.net>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F93911E8177 for <oauth@ietfa.amsl.com>; Wed, 27 Jul 2011 15:21:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level:
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SHNwikvMLhP0 for <oauth@ietfa.amsl.com>; Wed, 27 Jul 2011 15:21:59 -0700 (PDT)
Received: from smtprelay05.ispgateway.de (smtprelay05.ispgateway.de [80.67.31.100]) by ietfa.amsl.com (Postfix) with ESMTP id A548311E8097 for <oauth@ietf.org>; Wed, 27 Jul 2011 15:21:58 -0700 (PDT)
Received: from [70.25.120.2] (helo=[10.255.254.219]) by smtprelay05.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from <torsten@lodderstedt.net>) id 1QmCUF-0000em-Ok; Thu, 28 Jul 2011 00:21:56 +0200
Message-ID: <4E308F5C.9060408@lodderstedt.net>
Date: Wed, 27 Jul 2011 18:21:16 -0400
From: Torsten Lodderstedt <torsten@lodderstedt.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Brian Campbell <bcampbell@pingidentity.com>
References: <4E3052AA.1020902@lodderstedt.net> <CA55A84D.174B6%eran@hueniverse.com> <CA+k3eCQH346JmiQnExnK2HiXoKRD1Rm7wsbVTj6w_oUBsMLp=w@mail.gmail.com>
In-Reply-To: <CA+k3eCQH346JmiQnExnK2HiXoKRD1Rm7wsbVTj6w_oUBsMLp=w@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Df-Sender: torsten@lodderstedt-online.de
Cc: oauth <oauth@ietf.org>
Subject: Re: [OAUTH-WG] treatment of client_id for authentication and identification
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 27 Jul 2011 22:21:59 -0000

I personally think that would be more confusing than just adding the 
client_id parameter to the token endpoint request (independent of client 
authentication credentials).

Am 27.07.2011 18:17, schrieb Brian Campbell:
> I think that would be helpful, thanks.
>
>
> On Wed, Jul 27, 2011 at 12:43 PM, Eran Hammer-Lahav<eran@hueniverse.com>  wrote:
>> If you want, we can tweak section 2.4.1 to make client_secret optional if
>> the secret is the empty string. That will give you exactly what you want
>> without making the document any more confusing.
>> EHL

v2.23.0 | Report a Bug | By Email