If you cannot immediately update Google Chrome to version 146 or later, use one of the following workarounds for Google Chrome versions 142-145:
- Add resources to an access policy
Jamf's preferred solution is ensuring that every resource involved in a request, including CDN hosts, API endpoints, and login redirect targets, is covered by an access policy. Routing this traffic through the ZTNA tunnel prevents LNA enforcement. For more information about creating access policies for custom applications, see Adding a New Custom Application.
- Allow URLs with a Chrome enterprise policy
- If creating an access policy that covers all resources is not practical, the
LocalNetworkAccessAllowedForUrlsChrome enterprise policy can preapprove LNA access for specific origins. This suppresses the prompt for listed URLs without disabling LNA enforcement globally. Deploy this policy using the same steps described in Configuring ZTNA for Google Chrome Local Network Access, but use the following PLIST content, replacinghttps://[*.]example.comwith the origin URL of the affected application.<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyLists-1.0.dtd"> <plist version="1.0"> <dict> <key>LocalNetworkAccessAllowedForUrls</key> <array> <string>https://[*.]example.com</string> <string>https://app.internal.corp</string> </array> </dict> </plist>