[Draft] Fix canceling pin prompt causes host overload

remoting/protocol/third_party_authenticator_base.cc

Index: remoting/protocol/third_party_authenticator_base.cc
diff --git a/remoting/protocol/third_party_authenticator_base.cc b/remoting/protocol/third_party_authenticator_base.cc
index 9d6be72db2eabdb2d0c032bba867e9ea8c556ebc..8e66c89a369fcd14cfe070bd50d1ee93c147d2fd 100644
--- a/remoting/protocol/third_party_authenticator_base.cc
+++ b/remoting/protocol/third_party_authenticator_base.cc
@@ -34,6 +34,12 @@ ThirdPartyAuthenticatorBase::ThirdPartyAuthenticatorBase(
 ThirdPartyAuthenticatorBase::~ThirdPartyAuthenticatorBase() {
 }
 
+bool ThirdPartyAuthenticatorBase::has_auth_started() const {
+  if (token_state_ == ACCEPTED)
+    return underlying_->has_auth_started();
+  return false;

[Sergey Ulanov, 2014/03/24 18:42:36]

Third-party auth is started as soon as a message is sent to the peer.
underlying_ state is irrelevant here. So I think you need a started_ field
that's set to true when AddTokenElements() is called in GetNextMessage().

[kelvinp, 2014/03/24 23:11:39]

Done.

+}
+
 Authenticator::State ThirdPartyAuthenticatorBase::state() const {
   if (token_state_ == ACCEPTED)
     return underlying_->state();