IETF Logo Mail Archive

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

Brian Campbell <bcampbell@pingidentity.com> Wed, 27 July 2011 22:18 UTC

Return-Path: <bcampbell@pingidentity.com>
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 05F1321F88B7 for <oauth@ietfa.amsl.com>; Wed, 27 Jul 2011 15:18:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.956
X-Spam-Level:
X-Spam-Status: No, score=-5.956 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4]
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 jsoDn-nGCvbu for <oauth@ietfa.amsl.com>; Wed, 27 Jul 2011 15:18:20 -0700 (PDT)
Received: from na3sys009aog111.obsmtp.com (na3sys009aog111.obsmtp.com [74.125.149.205]) by ietfa.amsl.com (Postfix) with ESMTP id 3268721F8A4E for <oauth@ietf.org>; Wed, 27 Jul 2011 15:18:19 -0700 (PDT)
Received: from mail-qw0-f46.google.com ([209.85.216.46]) (using TLSv1) by na3sys009aob111.postini.com ([74.125.148.12]) with SMTP ID DSNKTjCOquVmnvhQOjPa7I4EoZkwl8QLOtA5@postini.com; Wed, 27 Jul 2011 15:18:20 PDT
Received: by mail-qw0-f46.google.com with SMTP id 3so1473751qwk.33 for <oauth@ietf.org>; Wed, 27 Jul 2011 15:18:18 -0700 (PDT)
Received: by 10.224.31.147 with SMTP id y19mr278034qac.243.1311805098153; Wed, 27 Jul 2011 15:18:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.11.68 with HTTP; Wed, 27 Jul 2011 15:17:48 -0700 (PDT)
In-Reply-To: <CA55A84D.174B6%eran@hueniverse.com>
References: <4E3052AA.1020902@lodderstedt.net> <CA55A84D.174B6%eran@hueniverse.com>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Wed, 27 Jul 2011 16:17:48 -0600
Message-ID: <CA+k3eCQH346JmiQnExnK2HiXoKRD1Rm7wsbVTj6w_oUBsMLp=w@mail.gmail.com>
To: Eran Hammer-Lahav <eran@hueniverse.com>
Content-Type: text/plain; charset="ISO-8859-1"
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:18:21 -0000

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