Setting the policy lets you list the URL patterns that specify which sites are automatically granted permission to access a USB device with the given vendor and product IDs on the login screen. Each item in the list requires both devices and urls fields for the policy to be valid. Each item in the devices field can have a vendor_id and product_id field. Omitting the vendor_id field will create a policy matching any device. Omitting the product_id field will create a policy matching any device with the given vendor ID. A policy which has a product_id field without a vendor_id field is invalid.
The USB permission model will grant the specified URL permission to access the USB device as a top-level origin. If embedded frames need to access USB devices, the 'usb' feature-policy header should be used to grant access. The URL must be valid, otherwise the policy is ignored.
Deprecated: The USB permission model used to support specifying both the requesting and embedding URLs. This is deprecated and only supported for backwards compatiblity in this manner: if both a requesting and embedding URL is specified, then the embedding URL will be granted the permission as top-level origin and the requsting URL will be ignored entirely.
Leaving the policy unset puts the global default value in use for all sites (no automatic access).
See https://cloud.google.com/docs/chrome-enterprise/policies/?policy=DeviceLoginScreenWebUsbAllowDevicesForUrls for more information about schema and formatting.
Example value:
[
{
"devices": [
{
"vendor_id": 1234,
"product_id": 5678
}
],
"urls": [
"https://google.com"
]
}
]
Registry Hive | HKEY_LOCAL_MACHINE |
Registry Path | Software\Policies\Google\ChromeOS |
Value Name | DeviceLoginScreenWebUsbAllowDevicesForUrls |
Value Type | REG_SZ |
Default Value |
Registry Hive | HKEY_LOCAL_MACHINE |
Registry Path | Software\Policies\Google\ChromeOS |
Value Name | DeviceLoginScreenWebUsbAllowDevicesForUrls |
Value Type | REG_MULTI_SZ |
Default Value |