Summary

Google Chrome 111.0.5563.65 introduced a security change that can affect Laserfiche Connector's ability to access Chrome's accessibility framework. This affects the Use JavaScript to detect controls option for Connector profiles. Existing profiles may no longer retrieve values and when configuring new profiles, Connector may not be able to detect and select elements on a page.

The issue also occurs when configuring Laserfiche Connector to work with Edge.

Workaround

Append the following parameter to the Windows shortcuts that open Chrome and Edge to allow the localhost origin for remote debugging.

--remote-allow-origins=localhost

To configure the Windows shortcut

1. Open the shortcut's properties.
   1. Right-click Google Chrome or Edge in the Start menu and select Open file location.
   2. Right-click the shortcut in the opened file location and select Properties.
2. In the Properties dialog box, navigate to the Shortcut tab.
3. In the Target text box, add a space after the last quotation mark and paste:
   • For Chrome: --remote-debugging-port=9222 --remote-allow-origins=localhost
   • For Edge: --remote-debugging-port=9322 --remote-allow-origins=localhost

   Note: The Edge debugging port is 9322, not 9222 as specified by Microsoft, to ensure Edge integrations do not conflict with Chrome integrations.

   Note: If you've changed the port number Laserfiche Connector uses, then replace 9222 or 9322 with the updated port number. You can check the port number being used in the LFC.exe.config file (located in the Laserfiche Connector installation directory).

4. The final value should look similar to the following example:

   "C:\Program Files\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222 --remote-allow-origins=localhost

5. Click OK to save your change.

Related Links

• Laserfiche Connector Documentation
• Chromium Issue 1422444