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

Torsten Lodderstedt <torsten@lodderstedt.net> Sat, 10 April 2010 07:05 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 94ACE3A6812 for <oauth@core3.amsl.com>; Sat, 10 Apr 2010 00:05:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.877
X-Spam-Level:
X-Spam-Status: No, score=-1.877 tagged_above=-999 required=5 tests=[AWL=0.372, BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 FEjjMOPvM34p for <oauth@core3.amsl.com>; Sat, 10 Apr 2010 00:05:57 -0700 (PDT)
Received: from smtprelay03.ispgateway.de (smtprelay03.ispgateway.de [80.67.31.30]) by core3.amsl.com (Postfix) with ESMTP id A689D3A6767 for <oauth@ietf.org>; Sat, 10 Apr 2010 00:05:57 -0700 (PDT)
Received: from p4fff0f64.dip.t-dialin.net ([79.255.15.100] helo=[127.0.0.1]) by smtprelay03.ispgateway.de with esmtpa (Exim 4.68) (envelope-from <torsten@lodderstedt.net>) id 1O0UlK-00085u-ED; Sat, 10 Apr 2010 09:05:50 +0200
Message-ID: <4BC0234D.8040700@lodderstedt.net>
Date: Sat, 10 Apr 2010 09:05:49 +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: Allen Tom <atom@yahoo-inc.com>
References: <C7E50B2D.2A788%atom@yahoo-inc.com>
In-Reply-To: <C7E50B2D.2A788%atom@yahoo-inc.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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 07:05:58 -0000

Hi Allen,

as I already posted, I don't think a size limit is a good idea.

Regarding your example: As per RFC-2109, 4KB is the minimum size that 
must be supported by user agents. The maximum size is not restricted:
"In general, user agents' cookie support should have no fixed limits.".

Moreover, other HTTP authentication mechanisms need much more than 4KB, 
For example, SPNEGO authentication headers can be up to 12392 bytes.

regards,
Torsten.

Am 10.04.2010 01:49, schrieb Allen Tom:
> 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
>