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 
<lainh...@us.ibm.com<mailto:lainh...@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 <jric...@mitre.org<mailto:jric...@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



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

Reply via email to