Explicitly wait for user policy before completing login.

chrome/browser/policy/browser_policy_connector.h

Index: chrome/browser/policy/browser_policy_connector.h
diff --git a/chrome/browser/policy/browser_policy_connector.h b/chrome/browser/policy/browser_policy_connector.h
index ef9848267e57ee6bc2a18c14d8836bd09f2a5707..393955a1e22769de55ba2082c18e13770bdf9ab8 100644
--- a/chrome/browser/policy/browser_policy_connector.h
+++ b/chrome/browser/policy/browser_policy_connector.h
@@ -9,6 +9,7 @@
 #include <string>
 
 #include "base/basictypes.h"
+#include "base/callback_forward.h"
 #include "base/memory/scoped_ptr.h"
 #include "base/memory/weak_ptr.h"
 #include "chrome/browser/policy/cloud_policy_constants.h"
@@ -112,8 +113,10 @@ class BrowserPolicyConnector : public content::NotificationObserver {
   // If |wait_for_policy_fetch| is true, the user policy will only become fully
   // initialized after a policy fetch is attempted. Note that Profile creation
   // is blocked until this initialization is complete.
+  // |ready_callback|, if not null, is invoked when the user policy is ready.

[Mattias Nissler (ping if slow), 2012/02/16 10:24:11]

Can you give some more detail on what the actual conditions for being "ready"
are? It's a bit unclear that "fully initialized" and "ready" are the same thing.

   void InitializeUserPolicy(const std::string& user_name,
-                            bool wait_for_policy_fetch);
+                            bool wait_for_policy_fetch,
+                            const base::Closure& ready_callback);
 
   // Installs a token service for user policy.
   void SetUserPolicyTokenService(TokenService* token_service);