IETF Logo Mail Archive

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

Brian Campbell <bcampbell@pingidentity.com> Thu, 28 July 2011 19:11 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 C3D0E21F85DE for <oauth@ietfa.amsl.com>; Thu, 28 Jul 2011 12:11:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.957
X-Spam-Level:
X-Spam-Status: No, score=-5.957 tagged_above=-999 required=5 tests=[AWL=0.020, 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 h-9toyFE6jWJ for <oauth@ietfa.amsl.com>; Thu, 28 Jul 2011 12:11:19 -0700 (PDT)
Received: from na3sys009aog105.obsmtp.com (na3sys009aog105.obsmtp.com [74.125.149.75]) by ietfa.amsl.com (Postfix) with ESMTP id 7443921F85FF for <oauth@ietf.org>; Thu, 28 Jul 2011 12:11:18 -0700 (PDT)
Received: from mail-qy0-f182.google.com ([209.85.216.182]) (using TLSv1) by na3sys009aob105.postini.com ([74.125.148.12]) with SMTP ID DSNKTjG0U7H/AHgLS0o9J+fIeYHvV8CKW3Um@postini.com; Thu, 28 Jul 2011 12:11:18 PDT
Received: by mail-qy0-f182.google.com with SMTP id 38so2200544qyk.6 for <oauth@ietf.org>; Thu, 28 Jul 2011 12:11:15 -0700 (PDT)
Received: by 10.224.182.15 with SMTP id ca15mr277581qab.343.1311880275103; Thu, 28 Jul 2011 12:11:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.11.68 with HTTP; Thu, 28 Jul 2011 12:10:44 -0700 (PDT)
In-Reply-To: <CA56CA21.1758B%eran@hueniverse.com>
References: <4E317125.7080006@lodderstedt.net> <CA56CA21.1758B%eran@hueniverse.com>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Thu, 28 Jul 2011 13:10:44 -0600
Message-ID: <CA+k3eCTguAGGC1xGuuA0Z2sRu7MNCdtsUnb-3V9vmz4CFwxBYw@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: Thu, 28 Jul 2011 19:11:20 -0000

I would be very much in favor of that addition/clarification.

On Thu, Jul 28, 2011 at 9:20 AM, Eran Hammer-Lahav <eran@hueniverse.com> wrote:
>
> [...] and I can also add a short note that public clients may use
> the client_id for the purpose of identification with the token endpoint.
> EHL
>

v2.23.0 | Report a Bug | By Email