[OAUTH-WG] Best practices on client_id
Antonio Tapiador del Dujo <atapiador@dit.upm.es> Fri, 25 January 2013 14:07 UTC
Return-Path: <atapiador@dit.upm.es>
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 A236421F881D for <oauth@ietfa.amsl.com>; Fri, 25 Jan 2013 06:07:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 dp-ryMptUNc7 for <oauth@ietfa.amsl.com>; Fri, 25 Jan 2013 06:07:29 -0800 (PST)
Received: from mail.dit.upm.es (mail.dit.upm.es [IPv6:2001:720:1500:42:215:c5ff:fef6:86e4]) by ietfa.amsl.com (Postfix) with ESMTP id 9536221F8CAC for <oauth@ietf.org>; Fri, 25 Jan 2013 06:07:28 -0800 (PST)
Received: from correo2.dit.upm.es (correo.dit.upm.es [IPv6:2001:720:1500:42:250:56ff:fea2:7367]) by mail.dit.upm.es (8.14.2/8.14.2) with ESMTP id r0PE7ReC000627 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <oauth@ietf.org>; Fri, 25 Jan 2013 15:07:27 +0100
Received: from [138.4.7.110] (seraph.dit.upm.es [138.4.7.110]) (authenticated bits=0) by correo2.dit.upm.es (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id r0PE7Pgh013728 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT) for <oauth@ietf.org>; Fri, 25 Jan 2013 15:07:27 +0100
Message-ID: <5102919D.5020601@dit.upm.es>
Date: Fri, 25 Jan 2013 15:07:25 +0100
From: Antonio Tapiador del Dujo <atapiador@dit.upm.es>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.11) Gecko/20121123 Icedove/10.0.11
MIME-Version: 1.0
To: "oauth@ietf.org" <oauth@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [OAUTH-WG] Best practices on client_id
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: Fri, 25 Jan 2013 14:07:29 -0000
Are there any recommendations for the authorization server when generating a client_id. Any security consideration? Should the client_id be a random string or it is save being just the database primary key? Kind regards.
- [OAUTH-WG] Best practices on client_id Antonio Tapiador del Dujo
- Re: [OAUTH-WG] Best practices on client_id Todd W Lainhart