jkakar/dashi

Dashi is a redirector

dashi's Issues

Add support for authentication

Dashi doesn't provide any means of authenticating requests. This is mostly okay since the dashboards it links to should have their own authentication, but even then, exposing details about the names of services and such is not good. OAuth2 with Heroku & Go looks like a good place to start researching how to add support for authentication.

Acceptance:

• Authentication is optional and can be turned on or off with config vars.
• A domain can be configured to allow blanket access. For example, "allow all example.com accounts".
• Authentication is remembered in the browser for a period of time (ideally configurable, but something like 30 days would be a reasonable default) so that users don't have to constantly auth when using the service.
• Credential rotation, if any is needed or possible, is documented in a playbook.

Include instructions to setup a Chrome search bookmark

Using Dashi with a Chrome search bookmark is a nice experience. We should include setup instructions in the README.

Acceptance:

• The README has clear instructions explaining how to setup a Chrome search bookmark.

Dashi doesn't work well with Firefox

Chrome automatically URL encodes input entered into the omnibox. Entering a URL like https://dashi.example.com/service dashboard will be converted to https://dashi.example.com/service%20dashboard automatically. I believe this will cause an error in Firefox. If Dashi treated the service as a path parameter, and the dashboard as another one, a Firefox user to enter a URL like https://dashi.example.com/service/dashboard, which would be easy to type.

Acceptance:

• Firefox users have a straightforward path to use Dashi.