Hello @EdwardD.90153 (Customer)​ Thank you for posting on our Community page!

This is actually a somewhat common issue with Okta Verify (especially on desktop with Okta FastPass) where the browser handoff fails, causing the app or browser to just spin and freeze on the redirect.

Here are the most common culprits and how to resolve them:

1. Loopback/Localhost Blocking (Desktop)

If this is happening on a Windows or macOS machine, Okta FastPass uses a local loopback port (usually http://localhost:65112/login/callback or similar) to hand off the authentication token from the browser back to the Okta Verify desktop app.

• The Fix: Ensure that no local firewalls, proxy software, or endpoint protection (like Sophos, Zscaler, or GlobalProtect) are blocking traffic to localhost or injecting SSL certificates into local loopback traffic. If your company recently rolled out a new network security tool, it might be intercepting this redirect.

2. Outdated Okta Verify App

There was a known bug in older versions of the Okta Verify desktop application that caused the "Verifying your identity" prompt to spin indefinitely without timing out.

• The Fix: Have the user manually update their Okta Verify app to the absolute latest version from the Windows Store, Mac App Store, or your internal software center.

3. Missing Local Network Access (LNA) for Silent Probing

If you are using endpoint management, Okta relies on silent probing to detect if the Okta Verify app is installed and running in the background.

• The Fix: Ensure that Local Network Access (LNA) is enabled for the Okta Verify app on the user's device so the browser can actually "see" the app and complete the redirect.

4. Browser Cache or Corrupted Session

Sometimes the browser gets stuck in a bad session state, especially if the user recently migrated to a new device but restored their settings from a backup.

• The Fix: Completely clear the browser's cache and cookies. If they are on a mobile device, deleting the Okta Verify app, clearing the default browser's cache, reinstalling the app, and re-enrolling the device often breaks the loop.

Thank you for reaching out to our Community and have a great day!

--

Help others in the community by liking or hitting Select as Best if this response helped you.