Open in the explorer

List of origins allowing all HTTP authentication

Type
Computer and user
GPO path
Computer Configuration › Policies › Administrative Templates › Brave Software › Brave › HTTP authentication User Configuration › Policies › Administrative Templates › Brave Software › Brave › HTTP authentication
Supported on
Microsoft Windows 7 or later
ADMX file
brave.admx
Internal name
brave/AllHttpAuthSchemesAllowedForOrigins

Explanation

Setting the policy specifies for which origins to allow all the HTTP authentication schemes Brave supports regardless of the AuthSchemes policy.

Starting in Brave 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
*

Registry

HKEY_LOCAL_MACHINE\Software\Policies\BraveSoftware\Brave
HKEY_CURRENT_USER\Software\Policies\BraveSoftware\Brave
Value name
not defined in the ADMX

Enable / disable values: not defined in the ADMX (see the options below).

PowerShell

PowerShell commands that write to the registry what the policy would write. Values in angle brackets (<…>) must be replaced.

Writing directly to the registry bypasses Group Policy: if a GPO manages this value, it will be rewritten at the next gpupdate; otherwise the value stays in place (the "tattooing" effect). Prefer a GPO or, locally, LGPO.exe. Run PowerShell as administrator for HKLM. Some policies need a restart or gpupdate /force.

Computer (HKLM)

Enable

# Enable: brave/AllHttpAuthSchemesAllowedForOrigins
$k = 'HKLM:\Software\Policies\BraveSoftware\Brave\AllHttpAuthSchemesAllowedForOrigins'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# List of origins allowing all HTTP authentication
# Non-additive list: existing values of the key are cleared first
if (Test-Path -Path $k) { (Get-Item -Path $k).Property | ForEach-Object { Remove-ItemProperty -Path $k -Name ([WildcardPattern]::Escape($_)) -ErrorAction SilentlyContinue } }
$values = @('<value1>', '<value2>')  # Replace the values with your own
$i = 1
foreach ($v in $values) { Set-ItemProperty -Path $k -Name ('' + $i) -Value $v -Type String; $i++ }

Disable

# Disable: brave/AllHttpAuthSchemesAllowedForOrigins
# No value is written in the "Disabled" state (nothing defined in the ADMX)

Revert to "Not configured"

# Revert to "Not configured": brave/AllHttpAuthSchemesAllowedForOrigins
$k = 'HKLM:\Software\Policies\BraveSoftware\Brave\AllHttpAuthSchemesAllowedForOrigins'
Remove-Item -Path $k -Recurse -Force -ErrorAction SilentlyContinue

User (HKCU)

Enable

Disable

Revert to "Not configured"

Options (1)

LabelControlRegistry valueREG typeConstraints / details
List of origins allowing all HTTP authenticationAllHttpAuthSchemesAllowedForOriginsDescList (table)listSoftware\Policies\BraveSoftware\Brave\AllHttpAuthSchemesAllowedForOriginsValues named “” + numberREG_SZ (values under the key)

Application

Brave (Brave Software) — November 2026 templates

Official templates downloaded on November 12, 2026.