Add support for public account policy to CloudPolicyClient.

chrome/browser/policy/proto/device_management_backend.proto

 // Copyright (c) 2012 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.
 
 syntax = "proto2";
 
 option optimize_for = LITE_RUNTIME;
 
 package enterprise_management;
 
@@ skipping 80 matching lines @@
 }
 
 message PolicyFetchRequest {
   // This is the policy type, which maps to D3 policy type internally.
   // By convention, we use "/" as separator to create policy namespace.
   // The policy type names are case insensitive.
   //
   // 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.
   optional int64 timestamp = 2;
 
   // Tell server what kind of security signature is required.
   enum SignatureType {
     NONE = 0;
     SHA1_RSA = 1;
   }
@@ skipping 140 matching lines @@
 }
 
 message TimePeriod {
   // [timestamp] is milli seconds since Epoch in UTC timezone.
   optional int64 start_timestamp = 1;
   optional int64 end_timestamp = 2;
 }
 
 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;
 }
 
 // This captures launch events for one app/extension or other installments.
 message InstallableLaunch {
   optional string install_id = 1;
 
   // Time duration where this report covers. These are required
   // and the record will be ignored if not set.
   optional TimePeriod duration = 2;
@@ skipping 39 matching lines @@
 
   // Error code, see enum above.
   optional ErrorCode error_code = 9;
 
   // Human-readable error message.
   optional string error_message = 10;
 }
 
 // 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.
   repeated ActiveTimePeriod active_period = 6;
 
   // The device location.
   optional DeviceLocation device_location = 7;
 }
 
 // Report session (a user on one device) level status.
@@ skipping 69 matching lines @@
 }
 
 // Request from the DMAgent on the device to the DMServer.  This is
 // container for all requests from device to server.  The overall HTTP
 // request MUST be in the following format:
 //
 // * HTTP method is POST
 // * Data mime type is application/x-protobuffer
 // * HTTP parameters are (all required, all case sensitive):
 //   * request: MUST BE one of
+//     * enterprise_check
+//     * ping
+//     * policy
 //     * register
+//     * status
 //     * unregister
-//     * policy
-//     * ping
-//     * status
-//     * enterprise_check
 //
 //   * 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:
 //      Authorization: GoogleDMToken token=<dm token from register>
 //
 //   * The Authorization header isn't used for enterprise_check requests, nor
 //     for register requests using OAuth. In the latter case, the OAuth token is
 //     passed in the "oauth" parameter.
 //
 // DeviceManagementRequest should only contain one request which matches the
@@ skipping 27 matching lines @@
 // Response from server to device.
 //
 // The server uses the following numbers as HTTP status codes
 // to report top-level errors.
 //
 // 200 OK: valid response is returned to client.
 // 400 Bad Request: invalid argument.
 // 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.
 // 901 Device Not Found: the device id is not found.
 // 902 Policy Not Found: the policy is not found.
 message DeviceManagementResponse {
   // Error message.
   optional string error_message = 2;
 
   // Register response
   optional DeviceRegisterResponse register_response = 3;
 
   // Unregister response
   optional DeviceUnregisterResponse unregister_response = 4;
 
   // Policy response.
   optional DevicePolicyResponse policy_response = 5;
 
   // Device status report response.
   optional DeviceStatusReportResponse device_status_report_response = 6;
 
   // Session status report response.
   optional SessionStatusReportResponse session_status_report_response = 7;
 
   // Auto-enrollment detection response.
   optional DeviceAutoEnrollmentResponse auto_enrollment_response = 8;
 }