Re: [OAUTH-WG] draft-richer-oauth-introspection-01 scope syntax

"Richer, Justin P." <jricher@mitre.org> Mon, 04 February 2013 16:23 UTC

Return-Path: <jricher@mitre.org>
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 7D93021F885B for <oauth@ietfa.amsl.com>; Mon, 4 Feb 2013 08:23:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.556
X-Spam-Level:
X-Spam-Status: No, score=-6.556 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H4K0HqQHf7t4 for <oauth@ietfa.amsl.com>; Mon, 4 Feb 2013 08:23:33 -0800 (PST)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 81A5221F86EB for <oauth@ietf.org>; Mon, 4 Feb 2013 08:23:33 -0800 (PST)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id E867F5310F72; Mon, 4 Feb 2013 11:23:32 -0500 (EST)
Received: from IMCCAS03.MITRE.ORG (imccas03.mitre.org [129.83.29.80]) by smtpksrv1.mitre.org (Postfix) with ESMTP id D2EB45310F6A; Mon, 4 Feb 2013 11:23:32 -0500 (EST)
Received: from IMCMBX01.MITRE.ORG ([169.254.1.25]) by IMCCAS03.MITRE.ORG ([129.83.29.80]) with mapi id 14.02.0318.004; Mon, 4 Feb 2013 11:23:32 -0500
From: "Richer, Justin P." <jricher@mitre.org>
To: Todd W Lainhart <lainhart@us.ibm.com>
Thread-Topic: [OAUTH-WG] draft-richer-oauth-introspection-01 scope syntax
Thread-Index: AQHOAuls0s8jUm5EhEujJWJMOkWRiZhqNe+A
Date: Mon, 4 Feb 2013 16:23:31 +0000
Message-ID: <B33BFB58CCC8BE4998958016839DE27E06885FEC@IMCMBX01.MITRE.ORG>
References: <OF3031393A.750F4AB2-ON85257B03.007AD84B-85257B03.007B56E7@us.ibm.com> <MLQM-20130130173104302-123870@mlite.mitre.org> <51099FBA.1060608@mitre.org> <OF0C4DFB94.D230FCE2-ON85257B08.0052DA9C-85257B08.00530629@us.ibm.com>
In-Reply-To: <OF0C4DFB94.D230FCE2-ON85257B08.0052DA9C-85257B08.00530629@us.ibm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.31.13.11]
Content-Type: multipart/alternative; boundary="_000_B33BFB58CCC8BE4998958016839DE27E06885FECIMCMBX01MITREOR_"
MIME-Version: 1.0
Cc: IETF oauth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] draft-richer-oauth-introspection-01 scope syntax
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: Mon, 04 Feb 2013 16:23:34 -0000

I got the same reading of the list as you, and I could go either way. I believe we absolutely must pick one or the other though.

If anyone has thoughts on the matter one way or the other, please speak up. The options are:

1) scopes are returned as a JSON array (current introspection text)
2) scopes are returned as a space-separated string (rfc6749 format for the "scope" parameter)


 -- Justin


On Feb 4, 2013, at 10:06 AM, Todd W Lainhart <lainhart@us.ibm.com<mailto:lainhart@us.ibm.com>>
 wrote:

Has there been any thinking or movement as to whether the scopes syntax stands as is, or aligns with 6749?  Of the folks who chose to respond, it seemed like the position was split.







From:        Justin Richer <jricher@mitre.org<mailto:jricher@mitre.org>>
To:        Todd W Lainhart/Lexington/IBM@IBMUS,
Cc:        IETF oauth WG <oauth@ietf.org<mailto:oauth@ietf.org>>
Date:        01/30/2013 05:34 PM
Subject:        Re: [OAUTH-WG] draft-richer-oauth-introspection-01 scope syntax
________________________________



I should add that this is also a bit of an artifact of our implementation. Internally, we parse and store scopes as collections of discrete strings and process them that way. So serialization of that value naturally fell to a JSON list.

-- Justin

On 01/30/2013 05:29 PM, Justin Richer wrote:
It's not meant to follow the same syntax. Instead, it's making use of the JSON object structure to avoid additional parsing of the values on the client side.

We could fairly easily define it as the same space-delimited string if enough people want to keep the scope format consistent.

-- Justin

On 01/30/2013 05:27 PM, Todd W Lainhart wrote:
That the scope syntax in draft-richer-oauth-introspection-01 is different than RFC 6749 Section 3.3, as in:


  "scope": ["read", "write", "dolphin"],

vs.

 scope = scope-token *( SP scope-token )
    scope-token = 1*( %x21 / %x23-5B / %x5D-7E )

Should introspection-01 follow the 6749 syntax for scopes?





_______________________________________________
OAuth mailing list
OAuth@ietf.org<mailto:OAuth@ietf.org>
https://www.ietf.org/mailman/listinfo/oauth




_______________________________________________
OAuth mailing list
OAuth@ietf.org<mailto:OAuth@ietf.org>
https://www.ietf.org/mailman/listinfo/oauth