en-US chrome computer user

List of origins allowing all HTTP authentication

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

Google Chrome

Path in the GPO console

Computer Configuration\Administrative Templates\Google\Google Chrome\HTTP authentication

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~HTTPAuthentication/AllHttpAuthSchemesAllowedForOrigins

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

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

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

Options

List of origins allowing all HTTP authentication
List (registry values) list list under Software\Policies\Google\Chrome\AllHttpAuthSchemesAllowedForOrigins

Description

Setting the policy specifies for which origins to allow all the HTTP authentication schemes Google Chrome supports regardless of the AuthSchemes policy. Starting in Google Chrome version 161, this policy applies only to destination server origins and does not apply to proxy server authentication challenges. To allow all HTTP authentication schemes for proxy servers, use the AllHttpAuthSchemesAllowedForProxies policy instead. Prior to version 161, proxy servers matching this policy are also allowed to use all HTTP authentication schemes unless AllHttpAuthSchemesAllowedForProxies is set. Format the origin pattern according to this format (https://support.google.com/chrome/a?p=url_blocklist_filter_format). Up to 1,000 exceptions can be defined in AllHttpAuthSchemesAllowedForOrigins. Wildcards are allowed for the host component (e.g., '*:8000' matches all hosts on port 8000). To match all schemes or all ports, omit the component entirely (e.g., 'example.com' matches any scheme and any port). A hostname (e.g., 'example.com') also matches its subdomains. To match a host exactly and exclude its subdomains, prepend it with a dot (e.g., '.example.com'). To match all origins, use a single asterisk ('*'). Example value: https://example.com example.com *:8000 *

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: List of origins allowing all HTTP authentication
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: Microsoft Windows 7 or later

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

PowerShell

# Exported from gporais.com
# Policy: List of origins allowing all HTTP authentication
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Windows 7 or later

$path = 'HKLM:\Software\Policies\Google\Chrome\AllHttpAuthSchemesAllowedForOrigins'
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