IETF Logo Mail Archive

Re: [OAUTH-WG] Proposed resolution for issue 26

Julian Reschke <julian.reschke@gmx.de> Fri, 07 October 2011 09:09 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E4D021F87E2 for <oauth@ietfa.amsl.com>; Fri, 7 Oct 2011 02:09:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.954
X-Spam-Level:
X-Spam-Status: No, score=-102.954 tagged_above=-999 required=5 tests=[AWL=-0.355, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SV48dXyCa38z for <oauth@ietfa.amsl.com>; Fri, 7 Oct 2011 02:09:31 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id B3F4D21F87FA for <oauth@ietf.org>; Fri, 7 Oct 2011 02:09:30 -0700 (PDT)
Received: (qmail invoked by alias); 07 Oct 2011 09:12:41 -0000
Received: from p5DCC3D4D.dip.t-dialin.net (EHLO [192.168.178.36]) [93.204.61.77] by mail.gmx.net (mp023) with SMTP; 07 Oct 2011 11:12:41 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+1iUgQvE61ha7D0DX6ve0cveQ0/H8JKCCdQwLDfS R54Jgv+YWdttSm
Message-ID: <4E8EC285.6080507@gmx.de>
Date: Fri, 07 Oct 2011 11:12:37 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: "Manger, James H" <James.H.Manger@team.telstra.com>
References: <4E1F6AAD24975D4BA5B16804296739435C1FC6A1@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAC4RtVDOPaMif55L6JAU4C8aERHgt6M0ntet7GKwgQJbUQKMZw@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739435C2148B5@TK5EX14MBXC285.redmond.corp.microsoft.com> <255B9BB34FB7D647A506DC292726F6E1128FF826E5@WSMSG3153V.srv.dir.telstra.com>
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E1128FF826E5@WSMSG3153V.srv.dir.telstra.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Proposed resolution for issue 26
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 07 Oct 2011 09:09:32 -0000

On 2011-09-28 05:50, Manger, James H wrote:
> I'll have another go trying to explain the problem I see with the scope parameter in the Bearer spec.
>
> Consider a French social network that decides to offer an API using OAuth2. It chooses 3 scope values for parts of the API related to family, friends, and business colleagues:
> * "famille"
> * "ami"
> * "collègues"
> Let's focus on the last scope.
>
> The site describes the scope and its semantics in HTML developer docs. That works.
>    <dt>coll&#xE8;gues</dt><dd>...</dd>
>
> Client apps construct authorization URIs to which users are sent. That works.
>    https://example.fr/authz?scope=coll%C3%A8gues...
> ...

Wait a minute. This only works if the spec explicitly states that 
non-ASCII characters need to be UTF-8 encoded before escaping (this is 
not part of "application/x-www-form-urlencoded".

Best regards, Julian

v2.23.0 | Report a Bug | By Email