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

Torsten Lodderstedt <torsten@lodderstedt.net> Sat, 10 April 2010 06:57 UTC

Return-Path: <torsten@lodderstedt.net>
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 5F7763A6A3C for <oauth@core3.amsl.com>; Fri, 9 Apr 2010 23:57:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.728
X-Spam-Level:
X-Spam-Status: No, score=-1.728 tagged_above=-999 required=5 tests=[AWL=0.520, BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001]
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 o9gIkBFZvMyZ for <oauth@core3.amsl.com>; Fri, 9 Apr 2010 23:57:06 -0700 (PDT)
Received: from smtprelay02.ispgateway.de (smtprelay02.ispgateway.de [80.67.31.40]) by core3.amsl.com (Postfix) with ESMTP id 00F9C3A699E for <oauth@ietf.org>; Fri, 9 Apr 2010 23:57:05 -0700 (PDT)
Received: from p4fff0f64.dip.t-dialin.net ([79.255.15.100] helo=[127.0.0.1]) by smtprelay02.ispgateway.de with esmtpa (Exim 4.68) (envelope-from <torsten@lodderstedt.net>) id 1O0Uck-0005sQ-5F; Sat, 10 Apr 2010 08:56:58 +0200
Message-ID: <4BC02133.70209@lodderstedt.net>
Date: Sat, 10 Apr 2010 08:56:51 +0200
From: Torsten Lodderstedt <torsten@lodderstedt.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: Eran Hammer-Lahav <eran@hueniverse.com>
References: <C7E557A0.32014%eran@hueniverse.com>
In-Reply-To: <C7E557A0.32014%eran@hueniverse.com>
Content-Type: multipart/alternative; boundary="------------070809040407020101020401"
X-Df-Sender: 141509
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: Sat, 10 Apr 2010 06:57:11 -0000

+1 no restriction, please

256 is much too short

Am 10.04.2010 07:16, schrieb Eran Hammer-Lahav:
> I would argue that for the spec to provide a token size limit that is 
> greater than 255 would cause more harm than good. This is not to say I 
> am supporting the 255 limit (I take no position on the matter -- yeah, 
> that happens rarely). If the spec provided a 4K limit, client 
> libraries are likely to codify that which will make them extremely 
> wasteful for 99% of the popular cases on the web today. A 4K limit 
> doesn't really improve interop since the limit is so high, no one is 
> likely to issue even bigger tokens with public APIs.
>
> The 255 limit keeps the token size within the most effective database 
> field size limit for this type of identifier. If we cannot reach 
> consensus on this size limit, I don't think the spec should say 
> anything. However, if I wrote a client library, I would make it use a 
> 255 default size limit and require a custom configuration to enable it 
> to use something else.
>
> So my proposal is 255 or no size guidance/restriction.
>
> EHL
>
>
> On 4/9/10 4:49 PM, "Allen Tom" <atom@yahoo-inc.com> wrote:
>
>     I think a good precedent would be to use the HTTP Cookie size
>     limit, which
>     is 4KB.
>
>     An OAuth Access Token is like an HTTP Authorization cookie.
>     They're both
>     bearer tokens that are used as a credentials for a client to access
>     protected resources on behalf of the end user.
>
>     All Oauth clients have to implement HTTP anyway, so 4KB sounds like a
>     reasonable limit.
>
>     Allen
>
>
>
>     > On Fri, Apr 9, 2010 at 3:14 AM, Luke Shepard
>     <lshepard@facebook.com> wrote:
>
>     >>
>     >> So, what is a reasonable limit for the token length?  1k? 2k?
>     4k? 5mb? I
>     >> suggest some language like this:
>     >>
>     >>
>
>     _______________________________________________
>     OAuth mailing list
>     OAuth@ietf.org
>     https://www.ietf.org/mailman/listinfo/oauth
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>