en-US chrome computer user

Allowed Origins for Proxied WebAuthn Requests from Remote Desktop Applications.

Verified with Google Chrome — updated on September 2, 2026 Supported on: Microsoft Windows 7 or later

Google Chrome

Path in the GPO console

Computer Configuration\Administrative Templates\Google\Google Chrome

Registry

HKLM Software\Policies\Google\Chrome
HKCU Software\Policies\Google\Chrome

Other deployment channels

Intune (ADMX ingestion)
./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~Miscellaneous/WebAuthenticationRemoteDesktopAllowedOrigins

OMA-URI published by Google. It requires the Chrome ADMX templates (chrome.admx, google.admx) to be imported in Intune first.

macOS / Linux preference WebAuthenticationRemoteDesktopAllowedOrigins
Android restriction WebAuthenticationRemoteDesktopAllowedOrigins
Supported platforms
  • Google Chrome (Linux) — since version 136
  • Google Chrome (Mac) — since version 136
  • Google Chrome (Windows) — since version 136
  • Google ChromeOS (Google ChromeOS) — since version 136
  • Google Chrome (Android) — since version 136

Google marks this policy "Platform Only": it cannot be set from the cloud console (Chrome Enterprise Core), only through platform management (GPO, Intune, plist…).

Source: official Chrome policy list, version 157.0.8103.79 Chrome Enterprise policy page

Options

Allowed Origins for Proxied WebAuthn Requests from Remote Desktop Applications.
List (registry values) list list under Software\Policies\Google\Chrome\WebAuthenticationRemoteDesktopAllowedOrigins

Description

A list of origins of remote desktop client apps that may execute WebAuthn API requests that originate from a browsing session on a remote host. Any origin configured in this policy can make WebAuthn requests for Relying Party IDs (RP IDs) that it would normally not allowed to be able to claim. Only valid HTTPS origins are allowed. Wildcards are not supported. Any invalid entries are ignored. This policy only applies to affiliated users. Example value: https://remotedesktop.google.com https://vdi.corp.example https://server:8080/

Export Builder

BETA

Configure the state, scope and options, then generate .reg, PowerShell, Intune and SCCM outputs — or add the setting to a multi-setting collection.

These exports write the registry — this is not a managed GPO. ⓘ

Scope

.reg file

Windows Registry Editor Version 5.00

; Exported from gporais.com
; Policy: Allowed Origins for Proxied WebAuthn Requests from Remote Desktop Applications.
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: Microsoft Windows 7 or later

[HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome\WebAuthenticationRemoteDesktopAllowedOrigins]
; List values: enter one value per line in the builder UI.
More formats (PowerShell, Intune, SCCM)

PowerShell

# Exported from gporais.com
# Policy: Allowed Origins for Proxied WebAuthn Requests from Remote Desktop Applications.
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Windows 7 or later

$path = 'HKLM:\Software\Policies\Google\Chrome\WebAuthenticationRemoteDesktopAllowedOrigins'
New-Item -Path $path -Force | Out-Null
# List values: enter one value per line in the builder UI.

Building a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.

Open the Builder

Embed this policy on your site

What to embed
Theme

Adds one script line: the theme follows your site’s appearance and the height fits the content. If your site blocks scripts, the embed follows the visitor’s system theme.

Preview