Message asking for access to local device when opening organization-shared maps

[MathiasHudock]

Some members of my organization have been seeing the below message when viewing Organization-shared web maps and web experiences in AGOL, specifically while using the Chrome browser:

This message doesn't seem to be related to a specific user type; two of our users have the same user type and role, but one gets the message, and the other doesn't. It also does not appear when viewing publicly-shared items. Has anyone seen this kind of thing before?

[Justin_Greco]

This is due to a security change in the latest version of Chrome:

https://developer.chrome.com/blog/local-network-access

This is affecting only our staff that are on the city network and only affecting services being served through our web adaptor.  I believe the issue is that our web servers resolve to a local IP address while connecting from our network.  It is not affecting anyone connecting from outside our network.

You can disable it in Chrome all together by going to chrome://flags/#local-network-access-check and switching the setting to "Disabled".

[TravisColeHC]

This just started happening to our county Map Viewer. It has major impacts on the functionality of the Experience Builder app. If you just close the pop-up or hit block, at the very least, our geolocator and print services stop functioning in the app. I haven't tested other functionality yet, but I suspect there are other things that also don't work properly.

[Justin_Greco]

We decided to just send out communication to all our users stating that it is safe to select allow as a short term solution.  The long term fix will be for our IT to set this enterprise Chrome policy:

https://chromeenterprise.google/policies/#LocalNetworkAccessAllowedForUrls

I don't know if there is something Esri can do about this, I do see that we can access our local network from the Map Viewer at www.arcgis.com, so I am thinking there must be something on their end allowing it, so maybe the same can be done to experience.arcgis.com.

The biggest issue for us has been our custom JavaScript applications hosted on our web servers.