IETF Logo Mail Archive

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

David Recordon <recordond@gmail.com> Wed, 10 March 2010 00:44 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 3F3123A67DB for <oauth@core3.amsl.com>; Tue, 9 Mar 2010 16:44:19 -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=[AWL=0.000, 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 lHg5kfKdWtYt for <oauth@core3.amsl.com>; Tue, 9 Mar 2010 16:44:18 -0800 (PST)
Received: from mail-iw0-f180.google.com (mail-iw0-f180.google.com [209.85.223.180]) by core3.amsl.com (Postfix) with ESMTP id 716C53A67AC for <oauth@ietf.org>; Tue, 9 Mar 2010 16:44:18 -0800 (PST)
Received: by iwn10 with SMTP id 10so1410666iwn.31 for <oauth@ietf.org>; Tue, 09 Mar 2010 16:44:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=hn1PB5tyf4QU1DsQg5qzviZqnex5p53Vgk/h8JPcOF0=; b=fNb8wQMFn3HYCZkXFIN1kEb2QcGGEyoOzKtQ5m37pSkgOuNPWRCYNq8RD8EaSjcqaz /ZPaGMAJNGxUwaTO4/atZidu5D49SN65///sSj74nKSsupTOud6MWZnuuPz8Z9qHQnt0 7Y3HMa1SjJ4AUAdmQB4tfIlzkX0g4QKHWOMTU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=DeQjN5KdeQjvYD9H55Uxz3PnEj+sLdB7LTpps/kcAPop8+pk7ZGfyv9ohdGDKFjWYV W/s2d5aTsXb7xJjiZvRkRNXMKyEpdeIPMp8x4xvoNJiceOxvjh5a99EYqjC6/BPaXMCH nQxyVyKk5KzebxPUHQJD6sBMifhoLqUr6lg7s=
MIME-Version: 1.0
Received: by 10.231.148.16 with SMTP id n16mr284162ibv.37.1268181859520; Tue, 09 Mar 2010 16:44:19 -0800 (PST)
In-Reply-To: <74caaad21003091623i8b7c343jc3bb806fe327492d@mail.gmail.com>
References: <fd6741651003091550t5a464496r57aae9a60c516599@mail.gmail.com> <74caaad21003091623i8b7c343jc3bb806fe327492d@mail.gmail.com>
Date: Tue, 09 Mar 2010 16:44:19 -0800
Message-ID: <fd6741651003091644x36c2b4f2tebf3ff476b054ea0@mail.gmail.com>
From: David Recordon <recordond@gmail.com>
To: Marius Scurtescu <mscurtescu@google.com>, Brian Eaton <beaton@google.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
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:44:19 -0000

I believe that Google wishes to encode information within access
tokens so that they can be verified in a stateless manner.  Brian, how
many characters do you need?


On Tue, Mar 9, 2010 at 4:23 PM, Marius Scurtescu <mscurtescu@google.com> wrote:
> 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