How to Build Social Apps with Operator Identity 26 February 2014
How to Build Social Apps with Operator Identity 26 February 2014 © 2013 Apigee – All Rights Reserved High Level Flow 3. Use API Exchange to discover user’s operator 1. Click on validate badge icon 2. Invoke User Verify MWC Badge API Attendees 6. Validate identity based on Open ID Connect response and return result to Application © 2013 Apigee – All Rights Reserved 4. Invoke standard Open ID Connect Calls OneAPI Exchange Discover 5. Translate and invoke operator backend. Capture user’s consent Open ID Connect Operator Backend Open ID Connect Operator Backend Open ID Connect Operator Backend …. Operator Backend 2 Digital Value Chain RESTful HTTP Usually using JSON User App Developer API API Team Backend Apigee Customers © 2013 Apigee – All Rights Reserved 3 Apigee Products Exchange API Networks OneAPI Mobile Mobile Mobile Operator Mobile Operator Operator Edge Point of Sale Push Notifications Events Location queries Datastore Users Data Partner Connections/Socia l Apps, APIs, Analytics ESB, SOA, App Servers, Databases Web Apps Backend Services Advanced API Services © 2013 Apigee – All Rights Reserved 4 Federated Identity Exposure • Augments existing Identity or Federated ID systems, internal and external • Interoperates with other Operator ID systems via API Exchange to address whole market Extensible Attributes API Services • Can store pointers to downstream ID, profile and context stores Profile and Persona ID Stores Contextualized queries Push Data Profile Stores Messages Social Graph Context Stores Federated User System © 2013 Apigee – All Rights Reserved 5 Enriching Operator Identity Exchange API Networks Advanced API Services Operator Identity Users Data Datastore OneAPI Location queries Events Push Notifications Connections/Socia l © 2013 Apigee – All Rights Reserved Enriched Identity Mobile Mobile Operator Mobile Operator Operator 6 Complexity Federated Identity Exposure “Social-Centric” “Account-Centric” See http://developers.facebook.com/docs/reference/api/user/ © 2013 Apigee – All Rights Reserved 7 5 Filters for evaluating profile attributes: • • • • • Does it provide value to the Subscriber? Is there a reasonable likelihood of Subscriber issuing a grant? Is it relevant in the context of a Transaction? Is it meaningful to the App Developer? Is it already stored with Operator’s existing profile? © 2013 Apigee – All Rights Reserved 8 Advanced API Services Users © 2013 Apigee – All Rights Reserved 9 Simple REST verb invocations… # Get Alan's user record with just a URL curl -X GET "https://api.usergrid.com/<org>/<env>/users/alanguirand" # Get Alan's user record by MSIDN curl -X GET "https://api.usergrid.com/<org>/<env>/users?ql=select%20*%20where%20phon e%3D'1-604-841-2109'" # Get Alan's user record with the query language and 'username' curl -X GET "https://api.usergrid.com/<org>/<env>/users?ql=select%20*%20where%20user name%3D'alanguirand'" © 2013 Apigee – All Rights Reserved 10 Demo © 2013 Apigee – All Rights Reserved 11 Posts and Followers © 2013 Apigee – All Rights Reserved 12 Apigee Advanced API Services Provides… • A RESTful, highly-distributed, no-SQL data store – – – – – Collections Entities Nested attributes Key-value pairs of structured and unstructured data Support for Collection and/or Entity-based relationships • Push Notifications – Apple iOS – Google Android • • • • • Location Services Access to social graphs Security: user management, UBAC, RBAC, token-based Easily integrated with our gateway directly or by callout policy JavaScript, iOS Native and Android Native (Java) SDKs © 2013 Apigee – All Rights Reserved 13 References GSMA OneAPI http://www.gsma.com/oneapi/ Apigee http://apigee.com http://apigee.com/docs/ http://apigee.com/about/api-best-practices Sign up for a free account © 2013 Apigee – All Rights Reserved 14 Questions © 2013 Apigee – All Rights Reserved 15 Thank you 24 February 2014 © 2013 Apigee – All Rights Reserved
© Copyright 2024