[OAUTH-WG] access_token and UUID
HAMANO Tsukasa <hamano@osstech.co.jp> Thu, 27 November 2014 03:06 UTC
Return-Path: <hamano@osstech.co.jp>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82E9D1A870B for <oauth@ietfa.amsl.com>; Wed, 26 Nov 2014 19:06:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.298
X-Spam-Level: *
X-Spam-Status: No, score=1.298 tagged_above=-999 required=5 tests=[BAYES_50=0.8, GB_I_LETTER=-2, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OzgNje1mqK3Z for <oauth@ietfa.amsl.com>; Wed, 26 Nov 2014 19:06:58 -0800 (PST)
Received: from shadow.osstech.co.jp (shadow.osstech.co.jp [153.121.71.31]) by ietfa.amsl.com (Postfix) with ESMTP id D98E01A1EB7 for <oauth@ietf.org>; Wed, 26 Nov 2014 19:06:57 -0800 (PST)
Received: from land.lan.osstech.co.jp (fnttkyo009065.tkyo.fnt.ngn2.ppp.infoweb.ne.jp [222.158.192.65]) by shadow.osstech.co.jp (Postfix) with ESMTP id 8FF3920175 for <oauth@ietf.org>; Thu, 27 Nov 2014 12:06:55 +0900 (JST)
Received: from plain.lan.osstech.co.jp.osstech.co.jp (fnttkyo009065.tkyo.fnt.ngn2.ppp.infoweb.ne.jp [222.158.192.65]) by land.lan.osstech.co.jp (Postfix) with ESMTPSA id E7C761811DA for <oauth@ietf.org>; Thu, 27 Nov 2014 12:06:26 +0900 (JST)
Date: Thu, 27 Nov 2014 12:06:27 +0900
Message-ID: <87sih5nxzg.wl%hamano@osstech.co.jp>
From: HAMANO Tsukasa <hamano@osstech.co.jp>
To: oauth@ietf.org
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (Gojō) APEL/10.8 EasyPG/1.0.0 Emacs/24.3 (x86_64-unknown-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: http://mailarchive.ietf.org/arch/msg/oauth/A61BzCVsfaoY_SfBw8R8__TErw0
Subject: [OAUTH-WG] access_token and UUID
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 27 Nov 2014 03:08:35 -0000
Hi, I have question about access_token generation. Would it be possible to use access_token that generated as UUID? It seems reasonable so UUID is regarded as safe ID generation algorithm. And in fact such OAuth 2.0 implementations exists. But there is a discrepancy between OAuth 2.0 spec and UUID spec around letter case. RFC 6749 says: > Unless otherwise noted, all the protocol parameter names and values > are case sensitive. > access_token > REQUIRED. The access token issued by the authorization server. RFC 4122 says: > The hexadecimal values "a" through "f" are output as lower case > characters and are case insensitive on input. I mean, access_token should be treated as case sensitive but UUID should be treated as case insensitive. What are your thoughts on that? Thank you. -- Open Source Solution Technology Corporation HAMANO Tsukasa <hamano@osstech.co.jp> fingerprint = 2285 2111 6D34 3816 3C2E A5B9 16BE D101 6069 BE55
- [OAUTH-WG] access_token and UUID HAMANO Tsukasa
- Re: [OAUTH-WG] access_token and UUID Justin Richer
- Re: [OAUTH-WG] access_token and UUID André DeMarre