Google Chrome is introducing a change that requires explicit permission before a website can send requests to the local network. This change is expected to be included in Google Chrome version 141.
This change impacts Duo Desktop and features such as Duo Trusted Endpoints and Duo Device Health Policies that are required on Davidson-issued devices. If the Duo Prompt cannot reach Duo Desktop, device information may not be collected, and authentications may fail.
Action required: Grant local network access in Chrome when prompted
Once Google Chrome has updated to the newest version (Chrome 141), upon the next attempt to access Blackbaud, Etrieve, Oracle, Banner Admin pages or the Davidson VPN and applications that require VPN access, you’ll see a local network access permission prompt from Chrome about Duo Desktop.
Choose Allow for local network access when prompted by Google Chrome version 141.
Instead of example.com, the prompt will say "duosecurity.com wants to look for and connect to any device on your local network."
To navigate to this setting manually, or if you clicked "Block" on the prompt:
- In Chrome, select the three vertically stacked dots in the upper right to bring up Chrome’s menu.
- Near the bottom of the menu, select Settings.
- From the Settings list, select Privacy and security.
- Underneath Privacy and Security options, select Site settings.
- At the bottom of the Permissions section, in the middle of the page, select Additional Permissions > Local network access.
- Next to Allowed to connect to any device on your local network, select Add.
- In the text box that appears, enter *.duosecurity.com (be sure to include the asterisk)