Webapp changes to support third party authentication

remoting/webapp/cs_third_party_auth_trampoline.js

Index: remoting/webapp/cs_third_party_auth_trampoline.js
diff --git a/remoting/webapp/cs_third_party_auth_trampoline.js b/remoting/webapp/cs_third_party_auth_trampoline.js
new file mode 100644
index 0000000000000000000000000000000000000000..f3c65c2b5cc17968d3d157a4e8fdfa4a7b499a7b
--- /dev/null
+++ b/remoting/webapp/cs_third_party_auth_trampoline.js
@@ -0,0 +1,10 @@
+// Copyright (c) 2012 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+var thirdPartyPath = '/talkgadget/oauth/chrome-remote-desktop/thirdpartyauth';
+
+if (window.location.pathname == thirdPartyPath) {
+  chrome.extension.sendMessage(window.location.href);

[Jamie, 2013/03/28 23:29:36]

It would be more future-proof to make this a structured message type. Something
like:

{type:'thirdPartyAuthToken', url:window.local.href}

Or it might be cleaner to parse it here--I don't have a strong opinion on that.

[rmsousa, 2013/03/29 04:08:21]

The sendMessage parameter is string typed. passing the redirectURL as the
message allows us to maintain the same interface as launchWebAuthFlow (that
calls its callback with the redirectURL when done).

+  window.close();
+}