On September 30, 2025, Google Chrome's M141 release introduced a new security prompt for Local Network Access on Windows, Mac, and Android devices. This affects FastPass users on Google Chrome, because FastPass invokes the native Okta Verify authenticator via the local server to complete authentication. The change is designed by Google to prevent CSRF attacks and local network fingerprinting, and also affects users who encounter a registered condition in their authentication policy.
In late October 2025, Okta added a new Early Access feature to help you make your users' experience with the prompt more intuitive.
What to do
Step 1: Enable Okta's Early Access feature
Enable the Remediation for blocked Local Network Access feature in each affected org.
Deep Link to the target Okta Admin Console.
Navigate to Settings > Features.
Toggle the Remediation for blocked Local Network Access feature.
Step 2: Notify FastPass users
Notify all customers using FastPass that they may see the following prompt when accessing Okta in Chrome:
<orgname>.okta.com wants to "Look for and connect to any device on your local network"
Users must click Allow. Clicking Block will cause FastPass authentication to fail.
If a user clicks Block
If you have enabled Okta's EA remediation feature:
The user will see a message on the Okta sign-in widget explaining that the browser is blocking communication with Okta Verify, with instructions to update the setting directly. If they follow the on-screen instructions they can restore access without contacting you. If they need additional assistance, share the manual instructions below.
If you have not enabled Okta's EA remediation feature:
Provide the user with these instructions to reset access directly in Chrome's site settings:




