Allow sync with 2-factor StrongAuth accounts in ChromeOS.

chrome/browser/chromeos/login/login_status_consumer.h

Index: chrome/browser/chromeos/login/login_status_consumer.h
diff --git a/chrome/browser/chromeos/login/login_status_consumer.h b/chrome/browser/chromeos/login/login_status_consumer.h
index da30369996c14998da3aba4aea381de98365794a..9aa90ebdf72a52b9c52d49e5d8844de13d2b7eac 100644
--- a/chrome/browser/chromeos/login/login_status_consumer.h
+++ b/chrome/browser/chromeos/login/login_status_consumer.h
@@ -95,6 +95,10 @@ class LoginFailure {
 class LoginStatusConsumer {
  public:
   virtual ~LoginStatusConsumer() {}
+  // Called when there was a failure during login, but the attempt may not fail
+  // (e.g. TWO_FACTOR failure). This should set any appropriate flags for
+  // consumption in OnLoginSuccess or OnLoginFailure.
+  virtual void SetLoginFailure(const LoginFailure& error) = 0;

[Chris Masone, 2010/11/17 01:11:09]

This mechanism is kind of ugly.  Why not just create some kind of flag
(sync_disabled?) in GaiaAuthConsumer::ClientLoginResult that carries this
information for you, since the only time we care is in the case of a TWO_FACTOR
"failure"

[stevenjb, 2010/11/17 23:48:41]

I agree that it was an awkward solution. I failed to notice that
ClientLoginResult was a struct that I could pass this information in. Made
changes to do so which simplify the CL significantly.

   // The current login attempt has ended in failure, with error |error|.
   virtual void OnLoginFailure(const LoginFailure& error) = 0;
   // The current login attempt has succeeded for