Gracefully handle token expiration about torus-cli HOT 4 OPEN

Thoughts @jeffandersen @jbowes @jelmersnoeck ?

from torus-cli.

You're gonna get a 401 back on requests which you're denied through ACL, so forcing you to log in again after that would suck.

This might involve adding a route specific to just testing auth, and ensure that we call that first?

Unless we can start storing the expiry alongside the token and just have the daemon check that locally first.

from torus-cli.

You're gonna get a 401 back on requests which you're denied through ACL, so forcing you to log in again after that would suck.

Yeah, we'd need to differentiate between an unauthorized access error and invalid session -- ideally through the error message type or some other piece of meta data.

from torus-cli.

We should probably differentiate between Forbidden access and not having a valid session (Unauthorized) to support this feature appropriately.

from torus-cli.