Add device policy definition for local accounts.

chrome/browser/policy/proto/chrome_device_policy.proto

Index: chrome/browser/policy/proto/chrome_device_policy.proto
diff --git a/chrome/browser/policy/proto/chrome_device_policy.proto b/chrome/browser/policy/proto/chrome_device_policy.proto
index 4b3a77aab8c7846eb9b1d0bc089d3926d01125b9..023520909c777d4f220cd4943d5d824c437c39b7 100644
--- a/chrome/browser/policy/proto/chrome_device_policy.proto
+++ b/chrome/browser/policy/proto/chrome_device_policy.proto
@@ -220,6 +220,15 @@ message SystemTimezoneProto {
   optional string timezone = 1;
 }
 
+message DeviceLocalAccountsProto {
+  // The list of account identifiers for the device-local accounts (i.e.
+  // accounts without an associated cloud-backed profile) that are available on
+  // the device. Account identifiers follow the conventions for email addresses,
+  // e.g. user@example.com. Policy-configured device-local accounts are on the

[Bin, 2012/11/13 20:03:49]

account_id will be in the format of email address, but it may contains illegal
characters for email address (e.g enterprise-configured public account). 

Can you add this to the comment to make it clear?

[Mattias Nissler (ping if slow), 2012/11/14 13:42:48]

Done.

+  // same domain that the device is enrolled to.
+  repeated string account_id = 1;

[Bin, 2012/11/13 20:03:49]

Should we define a singular DeviceLocalAccountProto here and defined a repeated
DeviceLocalAccountProto in ChromeDeviceSettingsProto? I am okay if we wrap
another layer on top of repeated DeviceLocalAccountProto.

If we ever want to put any additional fields into one single DeviceLocalAccount,
then it is hard to add in the current scheme.

[Mattias Nissler (ping if slow), 2012/11/14 13:42:48]

I prefer not to make ChromeDeviceSettingsProto.device_local_accounts repeated,
because there are probably going to be a few global device-local account
settings (auto-login for example).

Regarding adding more fields, you have a point. I figured that a simple repeated
string field would be easier to handle when I adjusted this yesterday. Then
again, better safe than sorry. Restored the old version.

+}
+
 message ChromeDeviceSettingsProto {
   optional DevicePolicyRefreshRateProto device_policy_refresh_rate = 1;
   optional UserWhitelistProto user_whitelist = 2;
@@ -241,4 +250,5 @@ message ChromeDeviceSettingsProto {
   optional StartUpUrlsProto start_up_urls = 18;
   optional PinnedAppsProto pinned_apps = 19;
   optional SystemTimezoneProto system_timezone = 20;
+  optional DeviceLocalAccountsProto device_local_accounts = 21;
 }