IETF Logo Mail Archive

[OAUTH-WG] Defining a maximum token length?

David Recordon <recordond@gmail.com> Tue, 09 March 2010 23:50 UTC

Return-Path: <recordond@gmail.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 97EFB3A6AAF for <oauth@core3.amsl.com>; Tue, 9 Mar 2010 15:50:34 -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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q72-sRyaqK-I for <oauth@core3.amsl.com>; Tue, 9 Mar 2010 15:50:34 -0800 (PST)
Received: from mail-gx0-f217.google.com (mail-gx0-f217.google.com [209.85.217.217]) by core3.amsl.com (Postfix) with ESMTP id CBBFC3A69B3 for <oauth@ietf.org>; Tue, 9 Mar 2010 15:50:33 -0800 (PST)
Received: by gxk9 with SMTP id 9so4387027gxk.8 for <oauth@ietf.org>; Tue, 09 Mar 2010 15:50:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=JkhTMEkqkj532vT29ks1SDj3TC4jCt2rNAG4il7emqA=; b=srwkAf2T3UPYT9daT8WJx09MyooFgIes3L5wehYh4AIP0ES0aKU79nyXMo4EOSstUa vogblr+P4Ue85hfJNaqnX5AVFUy+ZCh/wADVLT9u1YlxZNvqXNXkF5JxFiERdLRo4W18 biNaufWU25NgOIx0fkOwRj0HOdNBCLt1BLk9A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=VgaveYKMNkZS4/3ALHFNC2xGcoIKLGuYb4fIdouuhPqYmxYglR/UmvJLmD+mjflhyd YhlUl4IjQ2KpZStBSgjo8MQ4RxAYAOYRiiPK2R/iWaRXRaif5Qrp7Z8wG9wcvYlFM6yb 3l88/8vkhvDOOqXm6gBvN0kdjdIuRkFTYtkHk=
MIME-Version: 1.0
Received: by 10.100.236.5 with SMTP id j5mr1102459anh.60.1268178633021; Tue, 09 Mar 2010 15:50:33 -0800 (PST)
Date: Tue, 09 Mar 2010 15:50:32 -0800
Message-ID: <fd6741651003091550t5a464496r57aae9a60c516599@mail.gmail.com>
From: David Recordon <recordond@gmail.com>
To: OAuth WG <oauth@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [OAUTH-WG] Defining a maximum token length?
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: Tue, 09 Mar 2010 23:50:34 -0000

Ideally we'd limit the length of access and refresh tokens as well as
client keys and secrets to no more than 255 characters (a one byte
varchar in MySQL).  Is this an issue for anyone?

The OAuth 1.0 protocol specifically states:
Clients should avoid making assumptions about the size of tokens and
other server-generated values, which are left undefined by this
specification.

That seems like a poor idea when it comes to implementability of the
technology.  Why did OAuth 1.0 make that decision?

--David

v2.23.0 | Report a Bug | By Email