You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a token expires, or becomes invalid, the daemon does not destroy the session -- instead it will continue to attempt to use its currently stored session until the daemon is restarted or a user explicitly logs out through the CLI.
We should detect this scenario and destroy the session if a 401 is returned.
The text was updated successfully, but these errors were encountered:
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.
If a token expires, or becomes invalid, the daemon does not destroy the session -- instead it will continue to attempt to use its currently stored session until the daemon is restarted or a user explicitly logs out through the CLI.
We should detect this scenario and destroy the session if a 401 is returned.
The text was updated successfully, but these errors were encountered: