Support for Aggregators

[FabrizioMoggio]

An Aggregator (defined by GSMS in OPG.02) is a platform on top of the API Producer, consuming the API on behalf of an external system.

To verify if the external system is authorized to ask for the energy information about a specific application, the Transformation Function must be aware of the identity of the API Consumer.

The current release of the EFN API doesn't' not support this scenario.

[FabrizioMoggio]

The API authorization flow, even with the Aggregator, can provide the information about the identity of the API Consumer. So the authorization flow, before the API is actually consumed, can take care of the identification of both the Aggregator and the API Consumer. In this scenario there is nothing to add to the current release to support Aggregators.

This scenario assumes an AAA architecture that supports:

• Delegation
• Token exchange
• JWT with embedded consumer claims
• “on-behalf-of” model