Open in the explorer

TLS certificates that should be trusted by Google Chrome for server authentication with constraints

Type
Computer and user
GPO path
Computer Configuration › Policies › Administrative Templates › Google › Google Chrome › Certificate management settings User Configuration › Policies › Administrative Templates › Google › Google Chrome › Certificate management settings
Supported on
Microsoft Windows 7 or later
ADMX file
chrome.admx
Internal name
chrome/CACertificatesWithConstraints

Explanation

A list of TLS certificates that should be trusted by Google Chrome for server authentication, with constraints added outside the certificate. If no constraint of a certain type is present, then any name of that type is allowed.
Certificates should be base64-encoded. At least one constraint must be specified for each certificate.
See https://chromeenterprise.google/policies/?policy=CACertificatesWithConstraints for more information about schema and formatting.

Example value:

[
{
"certificate": "MIICCTCCAY6gAwIBAgINAgPluILrIPglJ209ZjAKBggqhkjOPQQDAzBHMQswCQYDVQQGEwJVUzEiMCAGA1UEChMZR29vZ2xlIFRydXN0IFNlcnZpY2VzIExMQzEUMBIGA1UEAxMLR1RTIFJvb3QgUjMwHhcNMTYwNjIyMDAwMDAwWhcNMzYwNjIyMDAwMDAwWjBHMQswCQYDVQQGEwJVUzEiMCAGA1UEChMZR29vZ2xlIFRydXN0IFNlcnZpY2VzIExMQzEUMBIGA1UEAxMLR1RTIFJvb3QgUjMwdjAQBgcqhkjOPQIBBgUrgQQAIgNiAAQfTzOHMymKoYTey8chWEGJ6ladK0uFxh1MJ7x/JlFyb+Kf1qPKzEUURout736GjOyxfi//qXGdGIRFBEFVbivqJn+7kAHjSxm65FSWRQmx1WyRRK2EE46ajA2ADDL24CejQjBAMA4GA1UdDwEB/wQEAwIBhjAPBgNVHRMBAf8EBTADAQH/MB0GA1UdDgQWBBTB8Sa6oC2uhYHP0/EqEr24Cmf9vDAKBggqhkjOPQQDAwNpADBmAjEA9uEglRR7VKOQFhG/hMjqb2sXnh5GmCCbn9MN2azTL818+FsuVbu/3ZL3pAzcMeGiAjEA/JdmZuVDFhOD3cffL74UOO0BzrEXGhF16b0DjyZ+hOXJYKaV11RZt+cRLInUue4X",
"constraints": {
"permitted_dns_names": [
"example.org"
],
"permitted_cidrs": [
"10.1.1.0/24"
]
}
}
]

Registry

HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome
HKEY_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/CACertificatesWithConstraints
$k = 'HKLM:\Software\Policies\Google\Chrome'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# TLS certificates that should be trusted by Google Chrome for server authentication with constraints
Set-ItemProperty -Path $k -Name 'CACertificatesWithConstraints' -Value '<value>' -Type String

Disable

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

Revert to "Not configured"

# Revert to "Not configured": chrome/CACertificatesWithConstraints
$k = 'HKLM:\Software\Policies\Google\Chrome'
Remove-ItemProperty -Path $k -Name 'CACertificatesWithConstraints' -ErrorAction SilentlyContinue

User (HKCU)

Enable

Disable

Revert to "Not configured"

Options (1)

LabelControlRegistry valueREG typeConstraints / details
TLS certificates that should be trusted by Google Chrome for server authentication with constraintsCACertificatesWithConstraintsText boxtextCACertificatesWithConstraintsREG_SZ
Max length: 1000000

Application

Google Chrome (Google) — November 2026 templates

Official templates downloaded on November 12, 2026.