Service Requests - ESPI lacks clarity for sending OAuth authorizations...

Advanced Search

Open Smart Grid - OpenSG > Help Desk > Service Requests > ESPI lacks clarity for sending OAuth authorizations in batch

Service Requests: ESPI lacks clarity for sending OAuth authorizations in batch

Service Request

ESPI lacks clarity for sending OAuth authorizations in batch

Details

If it is possible to send updates for resources requiring multiple distinct authorizations, the method for doing so needs to be defined. One possible way would be to add signature_method, signature, and nonce to Authorization and allow it to be included with BatchItemInfo. Otherwise, if Data Custodians are to verify valid authorization within batch POSTs, and reject submissions associated with resources to which the Authorized Thrid Party does not have authorization, that should be specified.

Customer

steve.van ausdall

Priority

(2) Normal

Service Representative

Assigned To

Keywords

ESPI; OpenADE; GreenButton

Comments

john.teeter1

(8/14/2012 3:31 PM): We had a brief discussion about "Batch" on OpenESPI call. While we didn't resolve the OAuth question directly, we figure there were two categories of things: "Batch" and "Bulk" where: Batch is the delivery of multiple resources under the auspices of a single Retail Customer's authorization. Bulk is the delivery of multiple resources under the auspices of 1 or more Retail Customer's authorization. I could do a "batch" request for multiple subscriptions owned by one user; or I might do a "bulk" request for multiple subscriptions each of which might be owned by different Retail Customers. The OAuth implications of the two (batch.vs.bulk) seem to be unique.

Status

Initiated

Resolution Type

Resolution Date

Mark for Knowledge Base

Resolution Time

Attachments