How Can Other API Implementations Benefit From Green Button's OAuth Inventions?

MyData API Patterns: OAUTH for Green Button

Conclusion

This article series describes the Green Button Initiative as a set of technologies that enable utility customers to share their usage information with third party service providers using the OAuth 2.0 protocol. To satisfy the Green Button use case, several small but significant extensions to the OAuth standard were needed, as described herein. With these enhancements the “scope” of OAuth applications has been substantially increased to the benefit of the data services that may be provided.

We hope that similar use cases in other domains might benefit from these techniques as well.

The following references are provided for enriched additional information for the reader about technologies and choices made in the design of the Green Button architecture.

• URI Conventions (OData Version 2.0)
• UML OMG Unified Modeling Language(OMG UML), Superstructure, V2.1.2, OMG, 2007-11-02
• IEC 61968-9 2nd Edition Application Integration at electric utilities - System interfaces for distribution management: Interfaces for meter reading and control, IEC 61968-9 2^nd Edition
• NAESB REQ.21 Energy Services Provider Interface (ESPI), NAESB REQ.21
• RFC 6750 The OAuth 2.0 Authorization Framework: Bearer Token Usage

Next in this Series

• Intro: Understanding the Green Button API Initiative and Why It Matters
• Part 1: Getting To Know The Primary Use Cases of The Green Button API initiative
• Part 2: Understanding The Requirements and Standards Behind The Green Button API Initiative
• Part 3: How Green Button Ingeniously Extended The OAuth Standard Without Forking It
• Part 4: How The Green Button API Initiative Takes Advantage of OAuth's Scope Parameter
• Part 5: How Green Button Made The "Pull-Only" OAuth Standard Support Push APIs Too
• Conclusion: How Can Other API Implementations Benefit From Green Button's OAuth Inventions?