Drill-through with Chrome: Blacklisting and Whitelisting 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 be blacklisted and whitelisted. For example, if an administrator blacklisted all messaging hosts by specifying "*" in the blacklist registry key, then drill-through from Oracle Smart View for Office would not work with Chrome.

In order to enable the Smart View native app which supports the Chrome extension (the app is C:\Oracle\SmartView\bin\SVNatvMsg.exe), then an administrator must add the name of the app, com.oracle.smartview.nmh (as specified in C:\Oracle\SmartView\bin\chromenmh.json) to the whitelist registry key.

Note:

Blacklisting is described here:

https://cloud.google.com/docs/chrome-enterprise/policies/?policy=NativeMessagingBlacklist

Whitelisting is described here:

https://cloud.google.com/docs/chrome-enterprise/policies/?policy=NativeMessagingWhitelist