Re: [OAUTH-WG] Scope parameter values for "authorization_code" and "client_credentials" based access tokens

["Donald Coffin" <[e-mail]>]

Bill,

 

Expiration of the access token is defined by the authorization server and returned to the client as part of the access token JSON response.  I’m not sure I understand the “scope name” and “max allowable records” portion of your question.  Can you clarify?

 

Some of the group believe the contents of the SCOPE parameter is a suggestion to the client of the data available from the resource server and NOT a limiting value of the data a client may access.  Can you comment on your interpretation of the meaning of the SCOPE parameter?

 

Best regards,

Don

Donald F. Coffin

Founder/CTO

 

REMI Networks

22751 El Prado Suite 6216

Rancho Santa Margarita, CA  92688-3836

 

Phone:      [phone]

Email:        <mailto:[e-mail]> [e-mail]

 

From: Bill Mills [mailto:[e-mail]] 
Sent: Monday, February 17, 2014 10:23 AM
To: Donald Coffin; 'Marty Burns'; [e-mail]
Cc: 'greenbutton-dev'
Subject: Re: [OAUTH-WG] Scope parameter values for "authorization_code" and "client_credentials" based access tokens

 

And how exactly does that apply to scope name, expiry, or max allowable records fetched?

 

On Monday, February 17, 2014 9:59 AM, Donald Coffin <[e-mail]> wrote:

Bill,

 

Our design does not include any identifiable information be passed within the token, as the standard being implemented (Energy Service Provider Interface) has the requirement that no personal identifiable information be exchanged between Third Parties (i.e. clients) and Data Custodians (i.e. authorization and resource servers).  Therefore, the tokens being generated are ubiquitous values with no direct information the recipient can use to access resource information.

 

Best regards,

Don

Donald F. Coffin

Founder/CTO

 

REMI Networks

22751 El Prado Suite 6216

Rancho Santa Margarita, CA  92688-3836

 

Phone:      [phone]

Email:       [e-mail]

 

From: Bill Mills [mailto:[e-mail]] 
Sent: Monday, February 17, 2014 9:10 AM
To: Donald Coffin; 'Marty Burns'; [e-mail]
Cc: 'greenbutton-dev'
Subject: Re: [OAUTH-WG] Scope parameter values for "authorization_code" and "client_credentials" based access tokens

 

Yes, token #1 with that scope could only access resource #3 and #4 in your example, the other resources don't allow that scope. The only solution in spec is to have the other resource owners allow a scope that token #1 has.

 

You're apparently overloading a bunch of stuff in the scope that most would put in the access token.  Are you trying to give a hint to the client about the token?

 

On Sunday, February 16, 2014 10:54 PM, Donald Coffin <[e-mail]> wrote:

Bill,

 

We understand, per [RFC 6749], the granted SCOPE does not have to match the requested SCOPE, however, in our application a client does an exchange of supported Authorization Server Scopes to ensure the resource owner is NOT asked by the client to select a SCOPE parameter the Authorization Server will be forced to override.

 

We also understand, per [RFC 6740], the SCOPE parameter is a space delimited list.  Therefore, the following two examples are not the same:

 

·         FB=4_5_15;IntervalDuration=900;BlockDuration=monthly;HistoryLength=13;BR=04

·         FB=4_5_15 IntervalDuration=900 BlockDuration=monthly HistoryLength=13 BR=04

 

The first string represents a single SCOPE parameter, but the second string represents five (5) different SCOPE parameters.  Our original definition of the SCOPE string used commas (“,”) where the first example has semi-colons (“;”), however, we found the Spring Security OAuth 2.0 framework treats commas as blanks to support a Facebook SCOPE implementation.  This has recently been refactored to support the [RFC 6749] SCOPE definition, as it was found that though Facebook’s documentation calls for commas as SCOPE parameter separators, this was never implemented by Facebook.

 

The following table defines a potential table of access tokens based on granted SCOPE strings:

 


Owner

SCOPE

Grant Type

Access Token

Accessible by Access Token


Client

FB=4_5_16;IntervalDuration=900;BlockDuration=monthly;HistoryLength=13;BR=05

Client_credentials

Token 1

NA**


RO 1

FB=4_5_15;IntervalDuration=900;BlockDuration=monthly;HistoryLength=13;BR=04

Code

Token 2

Token 2


RO 1

FB=4_5_16;IntervalDuration=900;BlockDuration=monthly;HistoryLength=13;BR=04

Code

Token 3

Token 3


RO 2

FB=4_5_15;IntervalDuration=900;BlockDuration=monthly;HistoryLength=13;BR=05

Code

Token 4

Token 4


RO 3

FB=4_5_16;IntervalDuration=900;BlockDuration=monthly;HistoryLength=13;BR=05

Code

Token 5

Token 5 & Token 1


RO 4

FB=4_5_16;IntervalDuration=900;BlockDuration=monthly;HistoryLength=13;BR=05

Code

Token 6

Token 6 & Token 1

 

** Token 1 is owned by the client and therefore does NOT own any resources for which access can be authorized.

 

The question we are attempting to resolve is which resources can the owner of Token 1 access given the above table?  If the owner of Token 1 is allowed to access ALL resources represented by Tokens 2 – 6, then we do not need to worry about identifying which resources can be accessed by using Token 1.  However, if Token 1 can only be used to access the resources authorized by resource owner (RO) 3 and 4, then what is the criteria that must be used to validate that Token 1, when used, is able to access the requested resource?

 

 

Best regards,

Don

Donald F. Coffin

Founder/CTO

 

REMI Networks

22751 El Prado Suite 6216

Rancho Santa Margarita, CA  92688-3836

 

Phone:      [phone]

Email:       [e-mail]

 

From: Bill Mills [mailto:[e-mail]] 
Sent: Sunday, February 16, 2014 10:02 PM
To: Marty Burns; Donald Coffin; [e-mail]
Cc: greenbutton-dev
Subject: Re: [OAUTH-WG] Scope parameter values for "authorization_code" and "client_credentials" based access tokens

 

The scope requested does not have to match the scope granted.  

 

Also note that space is the scope separator per the spec, so BR=04 is not equal to FB=4_5_15;IntervalDuration=900;BlockDuration=monthly;HistoryLength=13;BR=04 but it's your implementation of how you want to interpret scopes.

 

On Sunday, February 16, 2014 5:36 PM, Marty Burns <[e-mail]> wrote:

Don,

 

Good comment. One point – the authorizations covered by BulkId=04 would have Scopes of:

                        FB=4_5_15;IntervalDuration=900;BlockDuration=monthly;HistoryLength=13;BR=04

Marty

 

 

From: [e-mail] [mailto:[e-mail]] On Behalf Of Donald Coffin
Sent: Sunday, February 16, 2014 8:14 PM
To: 'Bill Mills'; [e-mail]
Cc: 'greenbutton-dev'
Subject: RE: [OAUTH-WG] Scope parameter values for "authorization_code" and "client_credentials" based access tokens

 

Bill,

 

Thanks for your reply, but I’m not sure you fully understand the situation I am attempting to resolve.

 

For example, does an access token obtained via the “client_credentials” request with the following SCOPE parameter:

                        BulkID=04

allow a client to ask for resources when the individual access token contained the following SCOPE parameter:

                        FB=4_5_15;IntervalDuration=900;BlockDuration=monthly;HistoryLength=13

 

The question is what individual access token authorization should be covered by the “client_credentials” based access token?

 

Best regards,

Don

Donald F. Coffin

Founder/CTO

 

REMI Networks

22751 El Prado Suite 6216

Rancho Santa Margarita, CA  92688-3836

 

Phone:      [phone]

Email:       [e-mail]

 

From: Bill Mills [mailto:[e-mail]] 
Sent: Saturday, February 15, 2014 8:30 PM
To: Donald Coffin; [e-mail]
Cc: greenbutton-dev
Subject: Re: [OAUTH-WG] Scope parameter values for "authorization_code" and "client_credentials" based access tokens

 

To tokens themselves don't differ based on how they are obtained unless you want them to.  No requirement to match scope to the client ID either, but again it's up to you.

 

You do want to get this right.  The challenge here is that your resource servers have to get updated to support new scopes.  If they support auto-updates then it's not quite as big a deal but it's still non-trivial.

 

-bill

 

 

 

On Saturday, February 15, 2014 7:01 PM, Donald Coffin <[e-mail]> wrote:

I would like to get the views and comments of the OAuth 2.0 IETF WG on the following design and implementation question:

 

I have an application that supports both “authorization_code” and “client_credentials” based access tokens.  The application allows a client to obtain data on a nightly basis for resource owners who have granted the application access to their data.  The client application retrieves energy usage information and can potentially need to retrieve data from a few accounts to several million accounts.  In order to eliminate the need for the client application to request the data from the resource server one account at a time, the client application has been designed to support “client_credentials” based access tokens.  Per [RFC 6749 Section 4.4 – “Client Credentials Grant”] The use of the “client_credentials” based access token will allow the client application to obtain access to the data with a single request, thus significantly reducing the amount of network traffic for both the client and the resource server.

 

The question the design team is struggling with is what should the Scope string be for the “client_credentials” based access token and should there be a single access token or can there be multiple “client_credentials” based access tokens?

 

The client application currently supports the following Scope definitions:

 

·         FB=4_5_15;IntervalDuration=900;BlockDuration=monthly;HistoryLength=13

·         FB=4_5_16;IntervalDuration=900;BlockDuration=monthly;HistoryLength=13

 

There are several allowable values for the FB=, IntervalDuration=, BlockDuration=, and HistoryLength= values.  At the moment, there are only two defined Scope values, but as you can see, there could easily be many more potential possibilities.  

 

The question being discussed, is does the “client_credentials” access token request Scope parameter need to match either of the above two strings or can it be something altogether different?  In the event the “client_credentials” access token request Scope parameter needs to match a defined Scope string, does that mean that there MUST be multiple “client_credentials” based access tokens?

 

Thanks in advance for helping clarify our understanding of the relationship between “authorization_code” and “client_credentials” based access tokens.

 

Best regards,

Don

Donald F. Coffin

Founder/CTO

 

REMI Networks

22751 El Prado Suite 6216

Rancho Santa Margarita, CA  92688-3836

 

Phone:      [phone]

Email:       [e-mail]

 


_______________________________________________
OAuth mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/oauth

-- 
You received this message because you are subscribed to the Google Groups "greenbutton-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [e-mail].
For more options, visit https://groups.google.com/groups/opt_out.