id.net APIs for Hosts
Download as PPT, PDF•0 likes•60 views
id.net APIs for Hosts discusses using id.net for user authentication and authorization. It covers topics like client-side vs server-side implementation, push vs pull data topologies, and available SDKs, libraries and APIs. The push API uses JSON responses with data, app ID, push ID and hash signature. While client-side is easier, server-side is more secure. id.net can help platforms grow by leveraging its user base and feature sets.
1 of 13
Download to read offline
More Related Content
What's hot (20)
Viewers also liked (20)
Ad
Similar to id.net APIs for Hosts (20)
PDF
The Good, the Bad and the Ugly of Migrating Hundreds of Legacy Applications ...Josef AdersbergerAd
Recently uploaded (20)
id.net APIs for Hosts
- 1. id.net APIs for Hosts HIGH LEVEL DISCUSSION ABOUT THE BEST WAYS TO USE ID.NET
- 2. Why use id.net? o Prioritizing the users o Economies of scale o Layered feature sets o Growing the audience
- 3. Topology What it looks like to use id.net
- 6. Mixed client and server side
- 7. Client Side VS. Server Side Client Server Easy to implement Requires a server Less secure More secure Difficult to track Easier to monitor Distributed Centralized On demand Preloaded or fetched
- 9. Push VS. Pull Push Pull Difficult to implement Easier to implement Server side Server or client side Faster updates Slow updates with long polling Less resource intensive* More resource intensive*
- 10. What is Available? SDKs oJavascript oFlash (legacy) Libraries oOmniauth-idnet oOauth2 Gem oSimple-oauth2 oOauth-server-php APIs oThe Oauth2 API set oSession API set (legacy) oThe old push API oThe new push API
- 11. Push API Application setting page on id.net Response format JSON { “data”: {}, “appid”: “123”, “pid”: “432”, “hash”: “sha256 sig” }
- 12. Conclusion o Using id.net can help a platform grow o Understanding the topology of client, server, and mixed networks o Client side and server side have many trade offs o Exploring the current push APIs could add efficacies to a project o There is still a strong use case for request/response pulling
- 13. What are your questions? Ideas, comments, feedback