Dashboard > ringside > ... > Design Documentation > Key Management
Key Management Log In | Sign Up   View a printable version of the current page.

Requirements

  • Network management
    • Administrator dictates list of networks that app developers are allowed to connect to
  • Enhance developer app to allow app-registration across multiple networks
    • App profile page: configure multiple Network IDs, API key, secret

Use Cases

  • Network Admin App
    • Registering a new network. Runningco, Voomaxer, and Facebook are all networks. In this use case, Voomaxer is a ringside server and also hosts the Voomaxer app. Runningco and Facebook use IDM to proxy app requests from their servers to Voomaxer. Voomaxer provides a "Network Administration" page that allows the admin to add/edit/remove a network with the following properties:
      • trust_key: ID remote network is identified by
      • trust_name: name of remote network
      • trust_auth_url: restserver URL or API url
      • login_url: points to login.php endpoint
      • canvas_url: fragment before app canvas URL
      • web_url: web root URL
      • social_url: base of IDM proxy URL, two social endpoints, trust.php and map.php
      • auth_class: class that is module which does auth (empty)
      • post_map_url: for custom registration procedure - URL user will be redirected to after mapping. Example - in runningco, 1) register 2) map 3) present things to do in post_map_url.
  • Enhancements to Developer App
    • App developer specifies API and secret keys for each network app connects to, and can add/edit/remove keys.
    • Privacy concern: app developers might not want to register all their API and secret keys with Ringside, is there a way to address this before release?
Added by Mike Schachter , last edited by Mike Schachter on Apr 15, 2008  (view change)
Labels: 
(None)