Webapp changes to support third party authentication

remoting/webapp/session_connector.js

Index: remoting/webapp/session_connector.js
diff --git a/remoting/webapp/session_connector.js b/remoting/webapp/session_connector.js
index 994746d50478da2712bd515f9964055a9f454b4f..2e4c7dddaa3554e3f6198f862485117eec4b9cd7 100644
--- a/remoting/webapp/session_connector.js
+++ b/remoting/webapp/session_connector.js
@@ -137,6 +137,7 @@ remoting.SessionConnector = function(pluginParent, onOk, onError) {
 remoting.SessionConnector.prototype.connectMe2Me = function(host, fetchPin) {
   this.hostId_ = host.hostId;
   this.hostJid_ = host.jabberId;
+  this.hostPublicKey_ = host.publicKey;

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

This feels like it should be a separate fix. Is it the case that the existing
auth methods didn't need this to be set, but thirdparty does?

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

Yes. Aside from ThirdPartyAuth, hostPublicKey is just stored in ConnectionToHost
and then never used.

[Jamie, 2013/03/29 18:19:24]

Generally, things like this should be in a separate CL. That way, if we ever
need to revert this one for any reason, we don't end up reverting the bugfix as
well.

   this.fetchPin_ = fetchPin;
   this.hostDisplayName_ = host.hostName;
   this.createSessionIfReady_();
@@ -274,7 +275,7 @@ remoting.SessionConnector.prototype.createSessionIfReady_ = function() {
     return;
   }
 
-  var securityTypes = 'spake2_hmac,spake2_plain';
+  var securityTypes = 'third_party,spake2_hmac,spake2_plain';
   this.clientSession_ = new remoting.ClientSession(
       this.hostJid_, this.clientJid_, this.hostPublicKey_, this.passPhrase_,
       this.fetchPin_, securityTypes, this.hostId_, this.connectionMode_,