Wire up component cloud policy to device local accounts.

chrome/browser/chromeos/extensions/device_local_account_management_policy_provider.cc

Index: chrome/browser/chromeos/extensions/device_local_account_management_policy_provider.cc
diff --git a/chrome/browser/chromeos/extensions/device_local_account_management_policy_provider.cc b/chrome/browser/chromeos/extensions/device_local_account_management_policy_provider.cc
index 9614868fb531e832e2c69bf0c7f439403fdbe351..4c85304b97a509f8ed73ed43c33be6826540614b 100644
--- a/chrome/browser/chromeos/extensions/device_local_account_management_policy_provider.cc
+++ b/chrome/browser/chromeos/extensions/device_local_account_management_policy_provider.cc
@@ -65,6 +65,9 @@ const char* kPublicSessionWhitelist[] = {
   "dhmdaeekeihmajjnmichlhiffffdbpde",  // Store.app demo
   "jeabmjjifhfcejonjjhccaeigpnnjaak",  // TweetDeck demo
   "pbdihpaifchmclcmkfdgffnnpfbobefh",  // YouTube demo
+
+  // Testing extensions:
+  "ongnjlefhnoajpbodoldndkbkdgfomlp",  // Show Managed Storage

[bartfab (slow), 2014/06/20 09:17:24]

You skipped process here :). We always ask Will or Sumit to sign off on
apps/extensions before adding them to the whitelist. Since this is an extension
we wrote ourselves, I am not concerned that it may be requesting excessive
permissions or doing something nasty but it would still be good to get their
blessing.

[Joao da Silva, 2014/06/20 11:48:45]

Thanks, I've notified Will and Sumit. As discussed offline, this file should at
least have a comment about that process; having an OWNERS file with set
no-parent would be even better.

 };
 
 }  // namespace