GreenButtonAlliance
User and RetailCustomer as separate entity
Currently ReatialCustomer & User is same entity and transaction data(e.g. linked to RetialCustomer). In our case, we will have delegated user (where primary customer may provide access to one or more users to view usage of certain accounts). Delegated user may authorize to third-party as well.
Dibyendujana,
While I understand the user case you have listed, it clearly violates The OAuth 2.0 Authorization Framework specification since it only allows a one-to-one authorization. Although it allows the client to function as a "delegated user" it clearly indicates such a role is reserved for resources either owned by the "delegated user" or granted to the "delegated user" by individuals.
This (the distinction b/t RetailCustomer and Delegated User) will be managed in conjunction with the support of the RetailCustomer.xsd in R1.3
