Drill-through with Chrome: Blocklist and Allowlist for Native Messaging
Drill-through with a Google Chrome browser can fail when Chrome is managed by enterprise policy. In this case, native messaging applications can use a blocklist or an allowlist. For example, if an administrator restricts access to all messaging hosts by using a blocklist (by specifying "
*
" in the blocklist registry key), then drill-through from Oracle Smart View for Office would not work with Chrome.
In order to enable the Smart View native application which supports the Chrome extension (the application is C:\Oracle\SmartView\bin\SVNatvMsg.exe
), then an administrator must add the name of the application, com.oracle.smartview.nmh
(as specified in C:\Oracle\SmartView\bin\chromenmh.json
) to the allowlist registry key.
Note:
-
Creating a blocklist is described here:
https://cloud.google.com/docs/chrome-enterprise/policies/?policy=NativeMessagingBlocklist
-
Creating an allowlist is described here:
https://cloud.google.com/docs/chrome-enterprise/policies/?policy=NativeMessagingAllowlist