Add support for public account policy to CloudPolicyClient.

chrome/browser/policy/proto/device_management_backend.proto

Index: chrome/browser/policy/proto/device_management_backend.proto
diff --git a/chrome/browser/policy/proto/device_management_backend.proto b/chrome/browser/policy/proto/device_management_backend.proto
index 97b75bdbc4b32ad770d8e7983a0c3f6e4472aa4d..a91ce2828b1e1a7f59361b8a76ce3129a265c032 100644
--- a/chrome/browser/policy/proto/device_management_backend.proto
+++ b/chrome/browser/policy/proto/device_management_backend.proto
@@ -98,7 +98,7 @@ message PolicyFetchRequest {
   // Possible values for Chrome OS are:
   //   google/chromeos/device => ChromeDeviceSettingsProto
   //   google/chromeos/user => ChromeSettingsProto
-  //   google/chromeos/unregistered_user => ChromeInitialSettingsProto (unused)
+  //   google/chromeos/publicaccount => ChromeSettingsProto
   optional string policy_type = 1;
 
   // This is the last policy timestamp that client received from server.
@@ -259,6 +259,9 @@ message TimePeriod {
 
 message ActiveTimePeriod {
   optional TimePeriod time_period = 1;
+
+  // The active duration during the above time period.
+  // The unit is milli-second.

[bartfab (slow), 2012/12/03 12:28:40]

This comment seems unrelated to the CL. But since you are adding it:
milliseconds should be in plural and without a dash.

[Mattias Nissler (ping if slow), 2012/12/03 13:50:39]

True. This is the text they have on the google3 side though, and I was just
syncing with that. Note that my original reason for the syncing (adding
settings_entity_id to PolicyData) Joao has meanwhile committed in a CL of his
own, but I was thorough and re-synced our version of this file with google3 and
he was not :)

If you feel strong, I can just drop this file.

[bartfab (slow), 2012/12/03 14:01:05]

I think being in sync with the server trumps any spelling nits. Thanks for
clarifying.

On 2012/12/03 13:50:39, Mattias Nissler wrote:

   optional int32 active_duration = 2;
 }
 
@@ -318,17 +321,21 @@ message DeviceLocation {
 
 // Report device level status.
 message DeviceStatusReportRequest {
+  // The OS version reported by the device is a platform version
+  // e.g. 1435.0.2011_12_16_1635.
   optional string os_version = 1;
   optional string firmware_version = 2;
 
-  // "Validated", "Dev". Same as verified mode.
+  // "Verified", "Dev". Same as verified mode.
   // If the mode is unknown, this field should not be set.
   optional string boot_mode = 3;
 
+  // Device active times collection since last report rpc call.
   // No longer used -- use active_period instead.
-  repeated TimePeriod active_time = 4 [deprecated=true];
+  repeated TimePeriod active_time = 4 [deprecated = true];
 
   // The browser version string as shown in the About dialog.
+  // e.g. 17.0.963.18.
   optional string browser_version = 5;
 
   // A list of periods when the device was active, aggregated by day.
@@ -418,19 +425,19 @@ message DeviceAutoEnrollmentResponse {
 // * Data mime type is application/x-protobuffer
 // * HTTP parameters are (all required, all case sensitive):
 //   * request: MUST BE one of
-//     * register
-//     * unregister
-//     * policy
+//     * enterprise_check
 //     * ping
+//     * policy
+//     * register
 //     * status
-//     * enterprise_check
+//     * unregister
 //
 //   * devicetype: MUST BE "1" for Android or "2" for Chrome OS.
 //   * apptype: MUST BE Android or Chrome.
 //   * deviceid: MUST BE no more than 64-char in [\x21-\x7E].
 //   * agent: MUST BE no more than 64-char long.
 // * HTTP Authorization header MUST be in the following formats:
-//   * For register and ping requests, using Gaia authentication:
+//   * For register and ping requests
 //     Authorization: GoogleLogin auth=<auth cookie for Mobile Sync>
 //
 //   * For unregister, policy and status requests:
@@ -478,7 +485,7 @@ message DeviceManagementRequest {
 // 401 Unauthorized: invalid auth cookie or DM token.
 // 403 Forbidden: device management is not allowed.
 // 404 Not Found: the request URL is invalid.
-// 410 Gone: device is unknown to the server.
+// 410 Device Not Found: the device id is not found.
 // 491 Request Pending: the request is pending approval.
 // 500 Internal Server Error: most likely a bug in DM server.
 // 503 Service Unavailable: most likely a backend error.