Created AttestationPolicyObserver.

chrome/browser/policy/browser_policy_connector.h

 // Copyright (c) 2012 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.
 
 #ifndef CHROME_BROWSER_POLICY_BROWSER_POLICY_CONNECTOR_H_
 #define CHROME_BROWSER_POLICY_BROWSER_POLICY_CONNECTOR_H_
 
 #include <string>
 
 #include "base/basictypes.h"
 #include "base/memory/ref_counted.h"
 #include "base/memory/scoped_ptr.h"
 #include "base/memory/weak_ptr.h"
 #include "chrome/browser/policy/cloud/cloud_policy_constants.h"
 #include "chrome/browser/policy/configuration_policy_handler_list.h"
 
 #if defined(OS_CHROMEOS)
 #include "chrome/browser/chromeos/policy/proxy_policy_provider.h"
 #endif
 
+#if defined(OS_CHROMEOS)
+namespace chromeos {
+namespace attestation {
+class AttestationPolicyObserver;
+}}

[Mattias Nissler (ping if slow), 2013/03/27 14:16:34]

braces on separate lines.

[dkrahn, 2013/03/27 21:20:44]

Done.

+#endif
+
 class PrefRegistrySimple;
 class PrefService;
 class Profile;
 
 namespace net {
 class URLRequestContextGetter;
 }
 
 namespace policy {
 
@@ skipping 181 matching lines @@
 
   scoped_ptr<DeviceManagementService> device_management_service_;
 
   // Used to initialize the device policy subsystem once the message loops
   // are spinning.
   base::WeakPtrFactory<BrowserPolicyConnector> weak_ptr_factory_;
 
 #if defined(OS_CHROMEOS)
   scoped_ptr<AppPackUpdater> app_pack_updater_;
   scoped_ptr<NetworkConfigurationUpdater> network_configuration_updater_;
+  scoped_ptr<chromeos::attestation::AttestationPolicyObserver>
+      attestation_policy_observer_;

[Mattias Nissler (ping if slow), 2013/03/27 14:16:34]

Not sure this really belongs here. While this device setting also be relevant to
consumer devices? If yes, you want to move this to e.g.
chrome_browser_parts_chromeos.cc or g_browser_process.

[dkrahn, 2013/03/27 21:20:44]

This is only for enterprise managed devices.  I wasn't sure where to put this, I
also considered putting it in DeviceCloudPolicyManagerChromeOS.  I chose here
because this is where a few other policy-reactive objects seem to be (e.g.
network_configuration_updater_).  Let me know where you think is best.

[Mattias Nissler (ping if slow), 2013/04/02 12:49:39]

The rule is basically that we put the observers wherever the code lives that is
concerned about the respective policy. In this case, that code doesn't exist
yet. Logically, it should probably be closer to
DeviceCloudPolicyManagerChromeOS, have you thought about how that solution would
look like?

[dkrahn, 2013/04/04 21:27:26]

Understood, I think it does fit well with DeviceCloudPolicyManagerChromeOS.

 #endif
 
   DISALLOW_COPY_AND_ASSIGN(BrowserPolicyConnector);
 };
 
 }  // namespace policy
 
 #endif  // CHROME_BROWSER_POLICY_BROWSER_POLICY_CONNECTOR_H_