Once this policy was updated to the new version or a whitelist entry added for the extension for the older policy version, it worked.ĮDIT: Please note that the above NativeMessagingBlocklist and NativeMessagingAllowlist are only supported in Chrome 86 and onwards. Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~NativeMessaging/NativeMessagingBlacklist This was the original problem setting within Intune in the custom OMA-URI format with no whitelist set: You can either add in NativeMessagingWhitelist with your exceptions or use the newer Chrome policy of NativeMessagingBlocklist. One of those policies (which is now deprecated by Google) - NativeMessagingBlacklist with a wildcard (*) blocks access to the Native Messaging API's. We use Chrome CIS Level 1 security benchmarks that use ADMX ingestion (Chrome ADMX). I did try older versions of Windows 10 (1903 etc.) and this wasn't the issue. ![]() ![]() ![]() Hi and McAninch, I managed after some lengthy testing, to get to the bottom of the problem for us.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
May 2023
Categories |