Handle authentication failures in the v2 app by restarting the app

remoting/webapp/crd/js/desktop_remoting.js

Index: remoting/webapp/crd/js/desktop_remoting.js
diff --git a/remoting/webapp/crd/js/desktop_remoting.js b/remoting/webapp/crd/js/desktop_remoting.js
index ab266268e261f9d811f05e1704148798f87e477a..3135c7d9acf65fe0cdfe38d12e87010fc000d643 100644
--- a/remoting/webapp/crd/js/desktop_remoting.js
+++ b/remoting/webapp/crd/js/desktop_remoting.js
@@ -279,6 +279,12 @@ remoting.DesktopRemoting.prototype.handleError = function(errorTag) {
   console.error('Connection failed: ' + errorTag);
   remoting.accessCode = '';
 
+  if (errorTag === remoting.Error.AUTHENTICATION_FAILED) {
+    remoting.setMode(remoting.AppMode.HOME);

[Jamie, 2015/01/23 23:33:26]

We should still show an error in this case. Would it be substantially more
complex to do that? I don't want to waste a lot of time polishing this UX, but
relaunching without telling the user you're going to do so is jarring

[kelvinp, 2015/01/28 00:26:45]

Ya, it would be some work to show the error cleanly, as the reconnect dialog is
hardcoded to reconnect (which doesn't fix any auth problem).  As discussed, I
think this would be a very rare scenario.  I would prefer to leave the code as
it is.

+    remoting.identity.handleAuthFailureAndRelaunch();
+    return;
+  }
+
   // Reset the refresh flag so that the next connection will retry if needed.
   this.refreshHostJidIfOffline_ = true;