App Settings about docnow

[raffazizzi]

@edsu I've made some changes to the authentication flow, just in my branch:

• if keys are not set, the app will show the home page, not the key settings page. This is because a non-setup user should still be able to land on the default home page as set by the admin (ie with instance location trends)
• if keys are not set, login will bring to the key settings page. The save button now also attempts to login
• to update keys users will (eventually, not yet) be able to do that from their profile page

The last point makes me think that "settings" (for now, just the keys) should actually be properties of the user rather than an app-wide setting. Although the server-side component will need just one set of keys to keep monitoring locations (and other operations), not one for each user. So who should set those keys? The admin? Do, in fact, other users need an application key to just log-in?

[edsu]

This all sounds good.

The CONSUMER_KEY and CONSUMER_SECRET key pair identifies the DocNow application. Each user will need to have an ACCESS_TOKEN and ACCESS_TOKEN_SECRET key pair so that the application can collect data on their behalf (using their quota).

I'm definitely open to ideas for where to store these keys and how to make them available from the API as long as those constraints hold.