Commit a7d2f182 authored by Yves Arrouye's avatar Yves Arrouye Committed by Commit Bot

Add device identification data for attestation-based registration

Add a new message and a field in the certificate-based registration
data that allows us to provide device identification during
registration.

Bug: b:153503823
Test: None
Change-Id: If6246345a52f79114622fb8d6c3cfc35fe81f635
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2141216Reviewed-by: default avatarPavol Marko <pmarko@chromium.org>
Commit-Queue: Yves Arrouye <drcrash@chromium.org>
Auto-Submit: Yves Arrouye <drcrash@chromium.org>
Cr-Commit-Position: refs/heads/master@{#758236}
parent aa1ba046
...@@ -185,7 +185,16 @@ message DeviceRegisterRequest { ...@@ -185,7 +185,16 @@ message DeviceRegisterRequest {
// domain from token. // domain from token.
optional string expected_enrollment_domain = 17; optional string expected_enrollment_domain = 17;
// Next id: 18. // Identification of the device that is not already available.
optional DeviceRegisterIdentification device_register_identification = 18;
// Next id: 19.
}
// Identification of a device used during its registration.
message DeviceRegisterIdentification {
// The Zero-Touch SN if a device has one.
optional string zero_touch_sn = 1;
} }
// Response from server to device register request. // Response from server to device register request.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment