How to authorize Redtrust native messaging in managed browsers
Overview
This guide explains how to authorize Redtrust native messaging in Chrome and Edge when enterprise policies restrict its use. It's intended for IT administrators who manage their organization's browsers.
Native messaging lets the extension communicate with the agent installed on the machine. To do so, the browser starts an intermediary program, the Redtrust host, and must allow it to run. While it's blocked, the extension can't communicate with the agent, even though it's installed and enabled.
For the values the agent writes on each machine, see Agent native messaging hosts.
If you install the agent with NO_CHROME=1 or NO_EDGE=1, the installer doesn't register the host for that browser, so there's nothing to authorize in it. With UNATTENDED_BROWSERS=1, the installer doesn't register the host for any browser.
Steps
Step 1: Add the Redtrust host to NativeMessagingAllowlist
NativeMessagingAllowlist is the policy that lists the authorized native messaging hosts. It takes precedence over NativeMessagingBlocklist, the blocklist, so adding the Redtrust host to the allowlist is enough.
This is the value to add for each browser:
| Browser | Value to add |
|---|---|
| Google Chrome | com.redtrust.monitorhost.chrome |
| Microsoft Edge | com.redtrust.monitorhost.msedge |
Add those values to the NativeMessagingAllowlist policy using the tool you manage browsers with, on the machines where the Redtrust agent is installed. Whatever the tool, the policy ends up as values under these Windows Registry keys on each machine:
| Browser | Policy key |
|---|---|
| Google Chrome | HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\NativeMessagingAllowlist |
| Microsoft Edge | HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\NativeMessagingAllowlist |
Inside the key, each host is a string value named with a consecutive number (1, 2, 3, and so on), so use the next free number. If the key doesn't exist, create it: Policies keys only appear once some policy is configured. Don't leave leading or trailing spaces in the value, because a stray space stops the browser from recognizing the host.
If you manage browsers with Active Directory/GPO, enable the policy in the native messaging section of the browser's administrative templates and add the host as a list entry. For example, the Chrome policy is under Administrative Templates > Google > Google Chrome > Native Messaging, and the Edge policy is under Administrative Templates > Microsoft Edge > Native Messaging. For more details about the policy, see its documentation for Chrome and Edge.
If you edit the registry directly on a machine you manage centrally, the next policy refresh can overwrite the change.
The agent registers the host under SOFTWARE\Google\Chrome\NativeMessagingHosts\, a key of its own that doesn't need any changes to configure this policy.
The policy is configured under SOFTWARE\Policies\Google\Chrome\ and determines which hosts the browser authorizes. You can see both locations in Agent native messaging hosts.
The value of this policy identifies the host. Authorization of the extension is managed separately through ExtensionInstallAllowlist, which isn't involved in this configuration.
NativeMessagingWhitelist and NativeMessagingBlacklist are the legacy names of these policies, and current Chrome and Edge versions ignore them. If you configure them, the browser lists them on its policy page with the error Unknown policy. and they have no effect. Always use NativeMessagingAllowlist.
Step 2: Apply the changes
The browser may apply the policy without restarting: the next step checks the result. If the extension still doesn't connect to the agent, close the browser completely, including background processes, so it reads the policy and the native messaging keys again.
For Chrome:
taskkill /IM "chrome.exe" /F
For Edge:
taskkill /IM "msedge.exe" /F
taskkill /F force-closes the browser, and the user loses open tabs and unsaved forms. Warn them first, or restart the machine during a maintenance window.
Step 3: Check the applied policy
- Open
chrome://policyin Chrome oredge://policyin Edge. - Click Reload policies and look for
NativeMessagingAllowlistin the list. - Check that the Redtrust host appears among its values and that the policy shows no error.
- To review the configuration in detail or send it to Redtrust support, click Export to JSON.
Summary
The Redtrust extension needs two things to talk to the agent: the registry key the installer creates on the machine, and the browser's permission to use that host. In environments that restrict native messaging by policy, adding the host name to NativeMessagingAllowlist, checking the result on the policy page, and restarting the browser if the extension still doesn't connect is enough.
Next steps
Once the host is authorized, you can:
- Configure your browser to allow the extension in incognito or InPrivate mode.
- Review the other enterprise policies that affect private browsing in The extension in incognito and InPrivate mode.
- Test if you can use a certificate.
Was this page helpful?