Brave Browser: 1.89.145 to 1.91.168

Setting the policy specifies for which origins to allow all the HTTP authentication schemes Brave supports regardless of the AuthSchemes policy. 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 [removed: whole origin][added: host component (e.g., '*:8000' matches all hosts on port 8000). To match all schemes] or [removed: parts of][added: all ports, omit] the [removed: origin, either the scheme, host, port.][added: 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: [removed: *.example.com][added: https://example.com example.com *:8000 *]

Setting the policy lets you make a list of URL patterns that specify sites for which Chrome can automatically select a client certificate. The value is an array of stringified JSON dictionaries, each with the form { "pattern": "$URL_PATTERN", "filter" : $FILTER }, where $URL_PATTERN is a content setting pattern. $FILTER restricts the client certificates the browser automatically selects from. Independent of the filter, only certificates that match the server's certificate request are selected. On Android[added: and iOS], Chrome can only select client certificates that it has provisioned itself; it cannot access certificates installed at the operating system level. Examples for the usage of the $FILTER section: * When $FILTER is set to { "ISSUER": { "CN": "$ISSUER_CN" } }, only client certificates issued by a certificate with the CommonName $ISSUER_CN are selected. * When $FILTER contains both the "ISSUER" and the "SUBJECT" sections, only client certificates that satisfy both conditions are selected. * When $FILTER contains a "SUBJECT" section with the "O" value, a certificate needs at least one organization matching the specified value to be selected. * When $FILTER contains a "SUBJECT" section with a "OU" value, a certificate needs at least one organizational unit matching the specified value to be selected. * When $FILTER is set to {}, the selection of client certificates is not additionally restricted. Note that filters provided by the web server still apply. Leaving the policy unset means there's no autoselection for any site. See https://cloud.google.com/docs/chrome-enterprise/policies/?policy=AutoSelectCertificateForUrls for more information about schema and formatting. Example value: {"pattern":"https://www.example.com","filter":{"ISSUER":{"CN":"certificate issuer name", "L": "certificate issuer location", "O": "certificate issuer org", "OU": "certificate issuer org unit"}, "SUBJECT":{"CN":"certificate subject name", "L": "certificate subject location", "O": "certificate subject org", "OU": "certificate subject org unit"}}}

Configure how Brave downloads the foundational GenAI model and uses for inference locally. When the policy is set to Allowed (0) or not set, the model is downloaded automatically, and used for inference. When the policy is set to Disabled (1), the model will not be downloaded, and the existing model (if already downloaded) will be deleted. On desktop platforms, model downloading can also be disabled by [removed: ComponentUpdatesEnabled.][added: setting ComponentUpdatesEnabled to false.]

When this policy is Enabled, anonymous reporting of usage and crash-related data about Brave to Google is recommended to be enabled by default. Users will still be able to change this setting. When this policy is Disabled, anonymous reporting is disabled and no usage or crash data is sent to Google. Users won't be able to change this setting. When this policy is not set, users can choose the anonymous reporting behavior at installation or first run, and can change this setting later. (For Google Chrome OS, see DeviceMetricsReportingEnabled.) [removed: On Microsoft® Windows®, this policy ][added: If the RestructureMetricsConsentSettings experiment ]is [removed: only available ][added: active ]on [removed: instances that are joined to a Microsoft® Active Directory® domain, joined to Microsoft® Azure® Active Directory® or enrolled in Chrome Enterprise Core. On macOS, ][added: the device and both ]this policy [removed: is only available on instances that ][added: and the MetricsReportingLevel policy ]are [removed: managed via MDM, joined to a domain via MCX or enrolled in Chrome Enterprise Core.][added: set, the MetricsReportingLevel policy takes precedence.]

When this policy is Enabled, anonymous reporting of usage and crash-related data about Brave to Google is recommended to be enabled by default. Users will still be able to change this setting. When this policy is Disabled, anonymous reporting is disabled and no usage or crash data is sent to Google. Users won't be able to change this setting. When this policy is not set, users can choose the anonymous reporting behavior at installation or first run, and can change this setting later. (For Google Chrome OS, see DeviceMetricsReportingEnabled.) [removed: On Microsoft® Windows®, this policy ][added: If the RestructureMetricsConsentSettings experiment ]is [removed: only available ][added: active ]on [removed: instances that are joined to a Microsoft® Active Directory® domain, joined to Microsoft® Azure® Active Directory® or enrolled in Chrome Enterprise Core. On macOS, ][added: the device and both ]this policy [removed: is only available on instances that ][added: and the MetricsReportingLevel policy ]are [removed: managed via MDM, joined to a domain via MCX or enrolled in Chrome Enterprise Core.][added: set, the MetricsReportingLevel policy takes precedence.]