Setting Up the Native Messaging Host

The Delinea Native Messaging Host provides a reliable method for storing settings, ensuring that deleting the browser cache does not affect them.

Without the Native Messaging Host, Web Password Filler runs normally, but the end user must supply the Secret Server URL and modify other settings as needed.

The Native Messaging Host contains one executable file and one configuration file. You install these files on your computer. Each time you launch your browser, the Native Messaging Host silently sends default configurations and settings to Web Password Filler.

You can prevent Web Password Filler from functioning on specific URLs by adding those URLs to an exclusion list. Web Password Filler does not access Secrets for URLs on the exclusion list, nor does it fill or auto-populate credentials or other information for those URLs.

To use an exclusion list with Web Password Filler, you must have the Native Messaging Host installed.

Downloading the Native Messaging Host

You can download the Native Messaging Host installer here.

Software Requirements

• .NET version 4.8 or later
• Delinea Web Password Filler version 3.10 or later

Supported Browsers

• Chrome
• Edge Chromium
• FireFox

You can find additional information regarding Native Messaging at:

• https://developer.chrome.com/extensions/nativeMessaging
• https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Native_messaging

Installing and Registering the Native Messaging Host

Installing and registering the Native Messaging Host streamlines management of Web Password Filler settings and ensures those settings remain intact even if the browser cache is cleared.

To install and register the Native Messaging Host: 

1. Copy the ThycoticMessagingHost.exe and settings.json files into an accessible directory, such as C:\Thycotic\Web Password Filler\.

2. Open a command window and enter the following command to register the Native Messaging Host with your browsers: 
   C:\Thycotic\Web Password Filler\ThycoticMessagingHost.exe --register

   The Native Messaging Host cannot interact with Web Password Filler until you complete this registration.

During registration, the Native Messaging Host creates a folder for each browser (Chrome, Edge, Firefox, and Opera) that contains the native messaging host configuration required by each browser. The process also creates registry entries for each browser, either in the current user or local machine registry.

For example, you find HKEY_CURRENT_USER\Software\Google\Chrome\NativeMessagingHosts\com.thycotic.wpf.host with a default value that is the path to the “native messaging host configuration” file. If you register using the EnableForAllUsers = true option, you must run the registration as an administrator.

After you successfully register the Native Messaging Host, it automatically checks the configuration file for updates each time you launch your browser. You do not need to unregister or re-register when you change other settings in settings.json; the changes take effect the next time you launch your browser.

If you manually add the Web Password Filler extension to your browser instead of installing it from the browser store, the extension ID changes. In this case, update the extension ID in settings.json and run the -–register command again before the extension can communicate with the Native Messaging host.

Uninstalling the Native Messaging Host

The Native Messaging Host no longer communicates with your browser extension once you uninstall it, helping maintain system security and performance.

To uninstall the Native Messaging Host:

1. Open a command window.

2. Run the following command: 
   C:\Program Files\Thycotic\Web Password Filler\ThycoticMessagingHost.exe --unregister

After you unregister, the Native Messaging Host no longer communicates with Web Password Filler.

Configuring Web Password Filler Settings

The Native Messaging Host manages Web Password Filler settings by modifying the settings.json file. Each time you launch your browser, the Native Messaging Host reads the default configurations and settings from the json file and silently sends them to Web Password Filler. WPF then updates the local storage with the new settings and configurations.

Establishing Default Settings and Browser-Specific Overrides

To customize how the Native Messaging Host manages settings for different browsers, edit the settings.json file. Modifying this file lets you set default options and create browser-specific overrides, ensuring each browser behaves according to your preferences.

To edit the settings.json file: 

1. Launch a text editor and open the settings.json file.

2. At the beginning of the settings.json file, write one line for each browser, and in that line enter the browser's identification code.

3. Label these initial lines as Browser IDs.

4. Add the next set of lines to define the default settings for the Native Messaging Host and label these lines as Default Settings.

5. Apply the default settings to all browsers in the settings.json file.

6. Create a new section for each browser that requires settings different from the default.

7. Label each new section as Default Overrides per Browser, then begin each override section with the browser's identification code.

8. List the settings in the same order as the default settings.

9. Enter a new value for each setting that differs from the default.

10. Allow the browser-specific value to override the default value for that browser.

11. Save your changes.

Below is an example of how to structure the settings.json file.

Formatting the settings.json File

The example settings.json file below sets the Secret Server base URL to https://<your-secretserver-domain>/SecretServer, where <your-secretserver-domain> should be replaced with your actual Secret Server domain name. It assigns the domain as 'local' and enables additional options for WPF. Web Password Filler.

We recommend validating the settings.json file prior to deployment to ensure that the JSON is formatted correctly. There are many free online tools for validating JSON files.

{
  "chromeExtensionId": "mfpddejbpnbjkjoaicfedaljnfeollkh",
  "edgeExtensionId": "kjldmpkefedgljefehmmfifbhnjngmbh",
  "operaExtensionId": "eemnnadjdifcpkcnpalolohpepihhbbo",
  "firefoxExtensionId": "dd1e31d5-3623-45cb-b1ad-64074d36b360@thycotic.com",
  "ConfigSSUrl": "https://SomeURL/SecretServer",
  "ConfigDomain": "local",
  "HideConfigPage": false,
  "HideSettingPage": false,
  "SettingUserSSLogin": true,
  "SettingPrompToSave": true,
  "SettingShowPopup": true,
  "SettingHideReadOnlyFolders": true,
  "SettingEnableAutoPopulate": true,
  "EnableForAllUsers": false,
  "PopupDefaultPosition": true,
  "ExactMatchUrl": false,
  "maxSessionRecordingLimit": 120,
  "Exclude": [ "http://*" ],
  "ExcludeException": [],
  "PerExtensionOverride": [
    {
      "id": "mfpddejbpnbjkjoaicfedaljnfeollkh",
      "ConfigSSUrl": "https://SomeURL/SecretServer",
      "ConfigDomain": "",
      "HideConfigPage": true,
      "HideSettingPage": false,
      "SettingUserSSLogin": true,
      "SettingPrompToSave": true,
      "SettingShowPopup": true,
      "SettingHideReadOnlyFolders": true,
      "SettingEnableAutoPopulate": true,
      "EnableForAllUsers": false,
      "PopupDefaultPosition": false,
      "ExactMatchUrl": true,
      "maxSessionRecordingLimit": 120,
      "Exclude": [
         "http://*",
         "http://endoftheinternet.com",
         "https://www.MyCompanySite.com",
         "https://live.com/"
       ],
      "ExcludeException": [
         "https:// MyCompanySite.com/Login.html",
         "https://login.live.com/login.srf"
       ]
    },
    {
      "id": "kjldmpkefedgljefehmmfifbhnjngmbh",
      "ConfigSSUrl": "https://localhost/SecretServer/",
      "ConfigDomain": "",
      "HideConfigPage": false,
      "HideSettingPage": false,
      "SettingUserSSLogin": false,
      "SettingPrompToSave": false,
      "SettingShowPopup": false,
      "SettingHideReadOnlyFolders": false,
      "SettingEnableAutoPopulate": false,
      "PopupDefaultPosition": false,
      "ExactMatchUrl": false,
      "maxSessionRecordingLimit": 120,
      "Exclude": [ "http://*" ],
      "ExcludeException": []
    },
    {
      "id": "dd1e31d5-3623-45cb-b1ad-64074d36b360@thycotic.com",
      "HideConfigPage": false
    },
    {
      "id": "eemnnadjdifcpkcnpalolohpepihhbbo"
    }
  ]
}

Configuring Boolean and Session Settings

Customize your settings.json file to control Web Password Filler’s behavior. Use boolean options and session durations to adjust menu placement, URL matching, and how long sessions are recorded.

To configure boolean and session settings: 

1. Open the settings.json file in your text editor.

2. Set the boolean setting for the menu position:.

   • Set it to true to place the menu in the upper right corner.

   • Set it to false to display the pop-up below the credentials field.

3. Set the boolean setting for URL matching:

   • Set it to true to accept only URLs that match the specified pattern.

   • Set it to false to allow partial URL matches.

4. Enter a session recording duration.

   The default value is 120 minutes, and the maximum is 480 minutes.

5. Scroll to the section labeled with the browser's identification code and enter a different session recording duration value to override the default for that specific browser.

6. Save the settings.json file.

Excluding Sites and Making Exceptions

You configure exclusions and exceptions in Web Password Filler to control which websites the extension interacts with, ensuring it fills credentials only on authorized login pages. This prevents the extension from interfering with registration forms or other non-login pages.

To exclude sites and make exceptions: 

1. Open the settings.json file for the Native Messaging Host using a text editor.

2. Go to the Native Messaging Host settings.

3. In the Exclude section, enter a wildcard such as https://* and/or http://* to exclude all sites.

4. In the ExcludeException section, add the exact URL of each login page you want WPF to interact with, omitting any query strings.

   For example, https://MyCompanySite.com/login.aspx

Use wildcards only in the Exclude section and always use the precise URL in the ExcludeException section.

Setting UI Behavior Based on Preferences

You can update UI behavior settings to control user access and tailor the application's configuration to your organization's need. These settings are controlled by editing the settings.json file, which the application reads to determine which preferences and server details are visible or changeable in the UI.

To set your UI behavior settings:

1. Open the settings.json file in a text editor.

2. Set each preference on the Preferences page to true or false.

   

3. Enter the Secret Server URL and Domain as strings (text wrapped in quotation marks).

   

You can choose to hide the preferences and configuration pages from end users by setting the appropriate flags in this file, preventing unauthorized changes.

Managing Error Messages

The native-messaging file records error messages and stores them in the same folder where you install the Native Messaging Host. You use the error messages in this file to troubleshoot issues or provide details when you contact Delinea support services.