This API is controlled by a permission policy 'DeviceAttributesAllowedForOrigins'. Finally it will be configured by Google Admin Console, but now it hasn't been ready. So you need to create a local policy file to overwrite it, then continue the testing. (See the detailed guide here
.) In general, you need to create a /etc/opt/chrome/policies/managed/test_policy.json file in those dev-mode devices, and add allowed origins in it.
At the origin-trial stage, we don't encourage you to use this web API in your real production devices. And yes, you have to access the devices and manually configure the policy for the moment. When we finish the Google Admin Console changes, and don't receive any critical concerns from developers in next months, we will announce GA shipment for this API. Then, you will be able to configure the policy for all managed devices more easily.
The current plan is running the original trial until Feb 23, 2022
Hi, We are about to start testing the API for a suite of kiosks being deployed to a chain of restaurants in the UK.
I am currently working remotely so do not have physical access to the Chrome OS devices we are testing on. I have registered the domain on Chrome Origin Trials but when I try to use the API on the test machines I get the following error...
The current origin cannot use this web API because it is not allowed by the DeviceAttributesAllowedForOrigins policy."
Do I need physical access to the devices to configure support for the new API?