[Draft] Fix canceling pin prompt causes host overload

remoting/protocol/third_party_authenticator_base.cc

 // Copyright 2013 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.
 
 #include "remoting/protocol/third_party_authenticator_base.h"
 
 #include "base/base64.h"
 #include "base/bind.h"
 #include "base/callback.h"
 #include "base/logging.h"
@@ skipping 16 matching lines @@
 
 ThirdPartyAuthenticatorBase::ThirdPartyAuthenticatorBase(
     Authenticator::State initial_state)
     : token_state_(initial_state),
       rejection_reason_(INVALID_CREDENTIALS) {
 }
 
 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();
   return token_state_;
 }
 
 Authenticator::RejectionReason
 ThirdPartyAuthenticatorBase::rejection_reason() const {
   DCHECK_EQ(state(), REJECTED);
 
@@ skipping 35 matching lines @@
 
 scoped_ptr<ChannelAuthenticator>
 ThirdPartyAuthenticatorBase::CreateChannelAuthenticator() const {
   DCHECK_EQ(state(), ACCEPTED);
 
   return underlying_->CreateChannelAuthenticator();
 }
 
 }  // namespace protocol
 }  // namespace remoting