Add a device policy for forced re-enrollment

BUG=chromium:778535
TEST=N/A

Change-Id: I709f8928127c5fc7a93404d93ea88ce1a3c38eba
Reviewed-on: https://chromium-review.googlesource.com/748890
Commit-Queue: Yves Arrouye <drcrash@chromium.org>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#513308}

components/policy/proto/chrome_device_policy.proto

@@ -900,6 +900,33 @@ message TPMFirmwareUpdateSettingsProto {
   optional bool allow_user_initiated_powerwash = 1;
 }
 
+message ForcedReenrollmentProto {
+  // Keep in sync with the backend enum (chrome_service_settings.proto).
+  enum ForcedReenrollmentMode {
+    // Default value if the mode cannot be parsed.
+    FORCED_REENROLLMENT_MODE_UNSPECIFIED = 0;
+
+    // Force user to re-enroll into the same domain that the device
+    // was enrolled in before the wipe. The device will use attestation-
+    // based enrollment if possible.
+    FORCED = 1;
+
+    // Suggest user to re-enroll into the same domain the device was
+    // enrolled in before the wipe. User can opt to enroll this device
+    // as consumer device instead, or enroll to another domain.
+    SUGGESTED = 2;
+
+    // No forced re-enrollment.
+    NONE = 3;
+  }
+
+  optional ForcedReenrollmentMode forced_reenrollment_mode = 1;
+
+  // Indicate whether the server needs an enrollment ID for attestation-based
+  // enrollment.
+  optional bool enrollment_id_needed = 2;
+}
+
 // Settings to control the minimum version that is allowed to sign in / stay
 // in session.
 message MinimumRequiredVersionProto {
@@ -980,4 +1007,5 @@ message ChromeDeviceSettingsProto {
       58;
   optional TPMFirmwareUpdateSettingsProto tpm_firmware_update_settings = 59;
   optional MinimumRequiredVersionProto minimum_required_version = 60;
+  optional ForcedReenrollmentProto forced_reenrollment = 61;
 }