The new token check logic will now close any open modal windows when the user's session ends, in case the user was configuring a new stack when the token expired.

On a similar note, the "auto-refresh" method we currently have of updating the UI does not seem to stop when the token expires. This leads to a spam (on both client and server) of 401 Unauthorized in the logs. Logging back into the UI does not stop the refresh log spam, but performing a hard refresh on the page will kill any running intervals.

To accomplish stopping these intervals when the session terminates, we could abstract the autorefresh / soft refresh logic out into its own AngularJS service, allowing us to call it from the context where we are performing the token check.