IETF Logo Mail Archive

Re: [OAUTH-WG] Defining a maximum token length?

Marius Scurtescu <mscurtescu@google.com> Wed, 10 March 2010 00:23 UTC

Return-Path: <mscurtescu@google.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 46BC43A67AF for <oauth@core3.amsl.com>; Tue, 9 Mar 2010 16:23:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.977
X-Spam-Level:
X-Spam-Status: No, score=-105.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 tP2zRPkXJCfq for <oauth@core3.amsl.com>; Tue, 9 Mar 2010 16:23:40 -0800 (PST)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 0D9EC3A6A16 for <oauth@ietf.org>; Tue, 9 Mar 2010 16:23:39 -0800 (PST)
Received: from wpaz1.hot.corp.google.com (wpaz1.hot.corp.google.com [172.24.198.65]) by smtp-out.google.com with ESMTP id o2A0NiOX007388 for <oauth@ietf.org>; Tue, 9 Mar 2010 16:23:44 -0800
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1268180624; bh=3clsp4DvLtZqFTkqjaY2+x2Qq38=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type:Content-Transfer-Encoding; b=KexWOmN4ru76mQ3kyjCy9OHEwduP7e7uLHlVa4lYTGSDyynnou2A740QzQp3elpGQ u0FGbcCoPB1hQOrY0ZEzA==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:from:date:message-id: subject:to:cc:content-type:content-transfer-encoding:x-system-of-record; b=DgkPDKe17ptteBqOLvV2yewCigC++/4qBoNRld95xDZgQlhWM+TFpKXVmLkq/ekmU +Mjy006HxzkQte6cvpVKw==
Received: from yxe41 (yxe41.prod.google.com [10.190.2.41]) by wpaz1.hot.corp.google.com with ESMTP id o2A0NhXA010068 for <oauth@ietf.org>; Tue, 9 Mar 2010 16:23:43 -0800
Received: by yxe41 with SMTP id 41so1196969yxe.20 for <oauth@ietf.org>; Tue, 09 Mar 2010 16:23:43 -0800 (PST)
MIME-Version: 1.0
Received: by 10.151.25.8 with SMTP id c8mr195803ybj.258.1268180623130; Tue, 09 Mar 2010 16:23:43 -0800 (PST)
In-Reply-To: <fd6741651003091550t5a464496r57aae9a60c516599@mail.gmail.com>
References: <fd6741651003091550t5a464496r57aae9a60c516599@mail.gmail.com>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Tue, 09 Mar 2010 16:23:23 -0800
Message-ID: <74caaad21003091623i8b7c343jc3bb806fe327492d@mail.gmail.com>
To: David Recordon <recordond@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [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: Wed, 10 Mar 2010 00:23:41 -0000

On Tue, Mar 9, 2010 at 3:50 PM, David Recordon <recordond@gmail.com> wrote:
> 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).

Add verification codes to the list as well.


> Is this an issue for anyone?

Not sure if anyone really wants to do this, but long tokens would
allow you to implement a stateless authorization server. A refresh
token can encrypt all the information needed to issue an access toke,
similar for a verification code. Such a server could either not deal
with revocations and replays, or track state only for revoked refresh
tokens and used verification codes.

That being said, I don't see a problem with limiting the lengths.


Marius

v2.23.0 | Report a Bug | By Email