AOSP builds do not support Device ID attestation
AOSP builds have different product & brand values than the ones flashed
onto the device's Keymaster in the factory.
As a result, Device ID attestation will not work on them correctly
because there is a mismatch between the values sent to Keymaster by the
platform and the values Keymaster is expecting to attest to.
Mark AOSP builds as not having this feature since it would affect all
AOSP builds on all devices.
Test: atest com.android.cts.devicepolicy.MixedDeviceOwnerTest#testKeyManagement
(cherry picked from commit 4260ee9282f9666821dbdb4e7dda6c65f605a6b2)
diff --git a/data/etc/aosp_excluded_hardware.xml b/data/etc/aosp_excluded_hardware.xml
index 013f278..c12f435 100644
@@ -18,4 +18,5 @@
<!-- This should be used to exclude this feature from aosp targets. As aosp configurations
may or may not have a valid location provider -->
<unavailable-feature name="android.hardware.location.network" />
+ <unavailable-feature name="android.software.device_id_attestation" />