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

"Donald F Coffin" <donald.coffin@reminetworks.com> Mon, 04 February 2013 18:55 UTC

Return-Path: <donald.coffin@reminetworks.com>
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 5C11121F87E1 for <oauth@ietfa.amsl.com>; Mon, 4 Feb 2013 10:55:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.239
X-Spam-Level:
X-Spam-Status: No, score=-1.239 tagged_above=-999 required=5 tests=[AWL=1.025, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334]
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 sweb1KHxfdwZ for <oauth@ietfa.amsl.com>; Mon, 4 Feb 2013 10:55:56 -0800 (PST)
Received: from oproxy9.bluehost.com (oproxy9.bluehost.com [69.89.24.6]) by ietfa.amsl.com (Postfix) with SMTP id 8D99221F8783 for <oauth@ietf.org>; Mon, 4 Feb 2013 10:55:51 -0800 (PST)
Received: (qmail 30804 invoked by uid 0); 4 Feb 2013 18:55:29 -0000
Received: from unknown (HELO host125.hostmonster.com) (74.220.207.125) by oproxy9.bluehost.com with SMTP; 4 Feb 2013 18:55:29 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=reminetworks.com; s=default; h=Content-Type:MIME-Version:Message-ID:Date:Subject:In-Reply-To:References:Cc:To:From; bh=Xk+Rfvp0/TlTV3/eHzHLx20/OfV4o/azZRlUfWOPz8c=; b=lVBqqqOT156Os2U7kgU1WXhrYG48jTdJ3b2ZhSOVZrl8PVGQMqTaEI1HM4WEu7hf4tei9TPVI66h1dwDxV9NQRN7+SFx+Ex0vBBhwVeEztsliUiHaBKtpn8hyT4hFGCk;
Received: from [68.4.207.246] (port=2827 helo=HPPavilionElite) by host125.hostmonster.com with esmtpa (Exim 4.80) (envelope-from <donald.coffin@reminetworks.com>) id 1U2RCT-0007c0-3F; Mon, 04 Feb 2013 11:55:29 -0700
From: "Donald F Coffin" <donald.coffin@reminetworks.com>
To: "'Richer, Justin P.'" <jricher@mitre.org>, "'Todd W Lainhart'" <lainhart@us.ibm.com>
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> <B33BFB58CCC8BE4998958016839DE27E06885FEC@IMCMBX01.MITRE.ORG>
In-Reply-To: <B33BFB58CCC8BE4998958016839DE27E06885FEC@IMCMBX01.MITRE.ORG>
Date: Mon, 4 Feb 2013 10:54:57 -0800
Message-ID: <00e101ce0309$21303700$6390a500$@reminetworks.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00E2_01CE02C6.130FB620"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHayEWWF0dQwkH9jF/aixGg/SYQlwGIUUn7AY7uQ+oB5ewA+wEpjK7xmB8nlqA=
Content-Language: en-us
X-Identified-User: {1395:host125.hostmonster.com:reminetw:reminetworks.com} {sentby:smtp auth 68.4.207.246 authed with donald.coffin@reminetworks.com}
Cc: John Adkins <jva2@pge.com>, Marty Burns <marty@hypertek.us>, Scott Crowder <scott.crowder@qadoenergy.com>, Dave Robin <drobin@automatedlogic.com>, John Teeter <john.teeter@peoplepowerco.com>, pmadsen@pingidentity.com, Edward Denson <ewd7@pge.com>, Uday Verma <uday.verma@ilinknet.com>, Ray Perlner <ray.perlner@nist.gov>, Anne Hendry <ahendry2@gmail.com>, Lynne Rodoni <mrodoni@semprautilities.com>, '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 18:55:59 -0000

Justin,

 

I am involved with the OpenESPI and OpenADE Task Force within the Smart Grid
Interoperability Panel (SGIP) which was established to engage stakeholders
from the Smart Grid Community in a participatory public process to identify
applicable standards, gaps in currently available standards, and priorities
for new standardization activities for the evolving Smart Grid. The SGIP
supports the National Institute of Standards and Technology (NIST) in
fulfilling its responsibilities under the 2007 Energy Independence and
Security Act.  My particular function is to chair the OpenESPI OAuth
sub-committee which is chartered with the integration of the OAuth 2.0
Protocol and the ESPI Standard.

 

Since OAuth 2.0 (RFC6749) has already established "scope" is a
space-separated string, it will be very confusing to implementers to no
define "scope" as a JSON array.  While a JSON array may be what the current
space-separated string is converted into when the application is written
using Java or one of its variants, there are other programming languages
that implementers may select to use.  Having to deal with two methods of
handling a "scope" response will require additional logic and merely
complicate the coding task.

 

Additional OAuth 2.0 specifications should not redefine data elements that
are already defined by RFC6749. Implementers should be able to rely on data
element definitions within RFC6749 being persistent throughout the OAuth
protocol framework.  If the OAuth introspective WG feels "scope" should be a
JSON array, then the WG should define a new data element rather than
changing the definition of an existing data element already defined by
RFC6749.

 

Best regards,

Don

Donald F. Coffin

Founder/CTO

 

REMI Networks

22751 El Prado Suite 6216

Rancho Santa Margarita, CA  92688-3836

 

Phone:      (949) 636-8571

Email:        <mailto:donald.coffin@reminetworks.com>
donald.coffin@reminetworks.com

 

From: Richer, Justin P. [mailto:jricher@mitre.org] 
Sent: Monday, February 04, 2013 8:24 AM
To: Todd W Lainhart
Cc: IETF oauth WG
Subject: Re: [OAUTH-WG] draft-richer-oauth-introspection-01 scope syntax

 

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>

 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> 
To:        Todd W Lainhart/Lexington/IBM@IBMUS, 
Cc:        IETF oauth WG <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
 <mailto:OAuth@ietf.org> OAuth@ietf.org
 <https://www.ietf.org/mailman/listinfo/oauth>
https://www.ietf.org/mailman/listinfo/oauth




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