platformKeys: Add policy and corporate key tagging.

chrome/browser/chromeos/platform_keys/key_permissions_policy_handlers.cc

+// Copyright 2015 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 "chrome/browser/chromeos/platform_keys/key_permissions_policy_handlers.h"
+
+#include "policy/policy_constants.h"
+
+namespace chromeos {
+
+KeyPermissionsPolicyHandler::KeyPermissionsPolicyHandler(
+    const policy::Schema& chrome_schema)
+    : policy::SchemaValidatingPolicyHandler(
+          policy::key::kKeyPermissions,
+          chrome_schema.GetKnownProperty(policy::key::kKeyPermissions),

[bartfab (slow), 2015/06/15 17:28:15]

Nit: #include "components/policy/core/common/schema.h"

[pneubeck (no reviews), 2015/06/17 08:59:56]

Done.

+          policy::SCHEMA_ALLOW_UNKNOWN) {
+}
+
+KeyPermissionsPolicyHandler::~KeyPermissionsPolicyHandler() {
+}
+
+void KeyPermissionsPolicyHandler::ApplyPolicySettings(
+    const policy::PolicyMap& /* policies */,
+    PrefValueMap* /* prefs */) {
+}

[bartfab (slow), 2015/06/15 17:28:15]

We normally use a pref as the vehicle to move policy values from here to other
subsystems. Even if there is no actual pref that expresses key permissions, the
idiomatic thing to do is to introduce such a (synthetic) pref and set its value
here, rather than accessing policy directly from KeyPermissions.

[pneubeck (no reviews), 2015/06/17 08:59:56]

Opinions on this seem to deviate as Mattias agreed that without equivalent user
setting it's fine to omit the pref.

If you don't feel strong about this, I'd prefer to keep it as is.

+
+}  // namespace chromeos