Add new BrowserForceSigninEnabeld policy option with future:true flag.

chrome/browser/policy/configuration_policy_handler_list_factory.cc

 // Copyright 2013 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/policy/configuration_policy_handler_list_factory.h"
 
 #include <limits.h>
 #include <stddef.h>
 
 #include <utility>
@@ skipping 346 matching lines @@
     prefs::kHardwareAccelerationModeEnabled,
     base::Value::TYPE_BOOLEAN },
   { key::kAllowDinosaurEasterEgg,
     prefs::kAllowDinosaurEasterEgg,
     base::Value::TYPE_BOOLEAN },
   { key::kAllowedDomainsForApps,
     prefs::kAllowedDomainsForApps,
     base::Value::TYPE_STRING },
   { key::kComponentUpdatesEnabled,
     prefs::kComponentUpdatesEnabled,
     base::Value::TYPE_BOOLEAN },

[pastarmovj, 2016/09/14 19:56:29]

Please revert the line removal.

[zmin, 2016/09/14 20:39:44]

Done.

-
 #if defined(ENABLE_SPELLCHECK)
   { key::kSpellCheckServiceEnabled,
     spellcheck::prefs::kSpellCheckUseSpellingService,
     base::Value::TYPE_BOOLEAN },
 #endif  // defined(ENABLE_SPELLCHECK)
 
   { key::kDisableScreenshots,
     prefs::kDisableScreenshots,
     base::Value::TYPE_BOOLEAN },
   { key::kAudioCaptureAllowed,
@@ skipping 187 matching lines @@
 #if !defined(OS_CHROMEOS) && !defined(OS_ANDROID)
   { key::kNativeMessagingUserLevelHosts,
     extensions::pref_names::kNativeMessagingUserLevelHosts,
     base::Value::TYPE_BOOLEAN },
   { key::kBrowserGuestModeEnabled,
     prefs::kBrowserGuestModeEnabled,
     base::Value::TYPE_BOOLEAN },
   { key::kBrowserAddPersonEnabled,
     prefs::kBrowserAddPersonEnabled,
     base::Value::TYPE_BOOLEAN },
+  { key::kBrowserForceSigninEnabled,

[pastarmovj, 2016/09/14 19:56:29]

I don't think the 'Browser' prefix is useful or rather it might make sense to
make it ForceBrowserSignin. I think you don't need the enabled suffix either.
The name already has a 'force' verb. In general I see ForceBrowserSignin as a
better name for the policy too.

PS. I think the reason the other policies here have this prefix is to
differentiate them from the same policies for ChromeOS. 

[zmin, 2016/09/14 20:39:44]

Yes, I use 'Browser' here just because of the two polices above as they are all
related to 'User Profile' but I don't know that is caused by ChromeOS. And yes,
I think ForceBrowserSignin is a good name since we have other 'Force' series as
well.

+    prefs::kBrowserForceSigninEnabled,
+    base::Value::TYPE_BOOLEAN },
 #endif  // !defined(OS_CHROMEOS) && !defined(OS_ANDROID)
 
 #if defined(OS_WIN)
   { key::kWelcomePageOnOSUpgradeEnabled,
     prefs::kWelcomePageOnOSUpgradeEnabled,
     base::Value::TYPE_BOOLEAN },
 #endif  // OS_WIN
 
 #if !defined(OS_ANDROID)
   { key::kSuppressUnsupportedOSWarning,
@@ skipping 292 matching lines @@
       SimpleSchemaValidatingPolicyHandler::MANDATORY_PROHIBITED)));
   handlers->AddHandler(
       base::MakeUnique<chromeos::KeyPermissionsPolicyHandler>(chrome_schema));
   handlers->AddHandler(base::WrapUnique(new DefaultGeolocationPolicyHandler()));
 #endif  // defined(OS_CHROMEOS)
 
   return handlers;
 }
 
 }  // namespace policy