WSO2Con EU 2015: Implementing an Open API for Smart Thermostats with WSO2′s API Manager
0 likes1,003 views
The document discusses the implementation of an open API for Quby's smart thermostat, focusing on the need for innovation and better access control. It evaluates different API management solutions, particularly WSO2, which is chosen for its fully open-source nature and support features. Future plans include migrating existing applications to the new API and optimizing internal API usage.
WSO2Con EU 2015: Implementing an Open API for Smart Thermostats with WSO2′s API Manager
- 1. Open API implementa.on for Quby’s Smart Thermostat Michiel Fokke IT Architect Quby
- 4. Mobile app
- 5. Tablet app
- 6. Tablet app
- 7. Current architecture Backend Applications Access Layer Asset ManagementInternet Internet Energy Displays Mobile devices VPN concentrator Utility Backend Mobile Backend Selfcare Authenticatio n Service
- 8. Current Architecture • Unmanaged à No visibility on alterna.ve use of API • Proprietary login à need for (encrypted) storage of selfcare password on device • Undocumented & unsupported API
- 10. Business Objec.ves • S.mulate innova.on by offering Open API • Build ecosystem with 3rd par.es • Enhance control on access • Enhance security
- 11. Solu.on Selec.on Criteria • Off the shelf product • Support for OAUTH2 • Developer selfcare • Extensibility • Open source • Affordable support • Nice to have: documenta.on portal
- 12. Solu.on candidates considered • MuleSoV • WSO2 • Pro’s for WSO2: • Fully Open Source • Clear pricing model for support and development
- 13. Open API solu.on design Backend Applications Access Layer Asset ManagementInternet Internet Energy Displays Mobile devices VPN concentrator Utility Backend WSO2 API Manager Self care Authenticatio n Service Mobile Backend
- 14. Customiza.ons • Custom Authen.cator Plugin to interface with proprietary authen.ca.on web service • User claims pass-‐through using JWT
- 15. Implementa.on Experiences • Stable soVware and easy to deploy • Bundling of components into product confusing at first • Elaborate documenta.on, but s.ll insufficient to develop plugin successfully (dev support solved that) • Solu.on quite complete, but lacks portal func.onality to withdraw access tokens by end-‐users
- 17. Eneco Toon Hackathon 2015
- 18. Eneco Toon Hackathon 2015 60+ par.cipants 14 working apps
- 19. Windows Apps
- 21. Apple watch app
- 22. Winner: Who pays Wae?
- 23. Winner: Who pays Wae? • Cost sharing app for students • Using smart plug usage data heps://youtu.be/HjufeirKJiI
- 24. Next steps • HA Setup for produc.on • Migrate own apps to new API • Start using API manager for internal API usage too
- 25. Thank You