Supported authentication schemes
Explanation
Setting the policy specifies which HTTP authentication schemes Google Chrome supports.
Leaving the policy unset employs all 4 schemes.
Valid values:
* basic
* digest
* ntlm
* negotiate
Note: Separate multiple values with commas.
Example value: basic,digest,ntlm,negotiate
Registry
HKEY_LOCAL_MACHINE\Software\Policies\Google\ChromeHKEY_CURRENT_USER\Software\Policies\Google\Chrome- 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: chrome/AuthSchemes
$k = 'HKLM:\Software\Policies\Google\Chrome'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# Supported authentication schemes
Set-ItemProperty -Path $k -Name 'AuthSchemes' -Value '<value>' -Type StringDisable
# Disable: chrome/AuthSchemes
# No value is written in the "Disabled" state (nothing defined in the ADMX)Revert to "Not configured"
# Revert to "Not configured": chrome/AuthSchemes
$k = 'HKLM:\Software\Policies\Google\Chrome'
Remove-ItemProperty -Path $k -Name 'AuthSchemes' -ErrorAction SilentlyContinueUser (HKCU)
Enable
Disable
Revert to "Not configured"
Options (1)
| Label | Control | Registry value | REG type | Constraints / details |
|---|---|---|---|---|
| Supported authentication schemesAuthSchemes | Text boxtext | AuthSchemes | REG_SZ | Max length: 1000000 |
Application
Google Chrome (Google) — November 2026 templates
Official templates downloaded on November 12, 2026.