search

gcivil-nyu-org / spring2020-cs-gy-9223-class

2 stars 14 forks source link

Grafana #531

Closed tianrunw closed 4 years ago

tianrunw commented 4 years ago

username and password feature on gfconfig

daisycrego commented 4 years ago

@tianrunw To do this change, we also need to change the way all error-handling is done on the UI. Currently, whenever there is an invalid API key, we display an error message.

When there is an invalid API key: (1) try and regenerate the API key using the current credentials (2) if for some reason we can't generate the key, prompt the user to re-enter their Grafana credentials (3) if we still can't generate valid API key for whatever reason, the user may eventually have to go to Grafana to generate the key (unlikely, but could happen)

The API key will eventually become invalid, so we need a mechanism to regenerate one and new error messages, otherwise we should keep it as is.