Users may encounter issues when authenticating with Okta FastPass on Android devices, such as being denied access to an app even with the required permissions. These issues often occur because the browser fails to communicate with the Okta Verify application due to device settings or network configurations, preventing Okta Fastpass and device management attestation from functioning. Adjusting application permissions, network settings, or browser configurations resolves most Okta FastPass authentication failures.

• Okta Verify
• Android
• Okta Identity Engine (OIE)

When authenticating using Okta FastPass, the browser must communicate with the Okta Verify application. Specific device configurations, network settings, or battery optimization restrictions prevent this communication. The Okta Verify application must run in the background during sign-in from both native applications and browsers to function correctly.

How are Okta FastPass authentication issues resolved on Android devices?

Perform the following troubleshooting actions as a first step:

• Navigate to the Okta Verify system settings and verify that notifications are enabled. A notification titled Sign in faster with Okta Verify displays in the notification tray unless the user mutes the Okta FastPass notification channel.

• Navigate to the system settings for Okta Verify and tap Battery (or App battery usage). Do not select Restricted. Select Optimized or a higher option.

• If the option is present, select Allow background activity for Okta Verify. 

• Switch the device network from Wi-Fi to mobile data, or from mobile data to Wi-Fi, to rule out network interference. Wait a few seconds and attempt authentication again after switching.

• Follow these steps to configure the Cloudflare Domain Name System (DNS) resolver on the Android device to rule out routing issues:

  1. Navigate to the device Settings and search for Private DNS.

  2. Select the Private DNS provider hostname and enter one.one.one.one.

NOTE: Using private DNS interferes with the ability to connect to captive portals. Turn off private DNS when attempting to connect to a captive portal.

• Navigate to the system settings for Okta Verify and tap Force stop. Relaunch the Okta Verify application and try signing in again.

How are browser desktop site mode issues resolved?

Follow these steps to ensure the Android browser does not operate in desktop mode, which causes Okta to detect the device incorrectly as an incompatible Linux desktop:

1. Open the browser settings.

2. Disable Desktop site (or Desktop mode). Android tablet devices often use this setting as the default.

3. Review the Google Chrome Help documentation regarding desktop mode settings for further configuration details.

How are redirection issues resolved for non-Chrome browsers?

Modify the following settings depending on the browser in use to prevent redirection failures:

• Enable Open links in other apps for non-Chrome browsers.

• Disable Open external links in Brave when using the Brave browser.

How are Okta Verify sign-in issues resolved in Android WebView?

Okta FastPass does not support WebView in native Android applications. Authentication issues occur when Okta Verify fails to run in the background or when the user installs the application in both personal and work profiles. Apply the following workarounds to resolve Android WebView authentication failures:

• Launch the Okta Verify application before attempting to sign in to the application requiring authentication.

• Enable notifications for Okta Verify in the device settings.

• Verify the App battery usage for Okta Verify does not have the Restricted option selected in the device settings.

• Configure Okta Verify to run in the background without power-saving restrictions by adding it to the list of applications exempt from battery optimization (often labeled Never sleeping apps or No restrictions).

• Disable general operating system settings that automatically put unused applications to sleep (such as Put unused apps to sleep) if Okta Verify cannot receive a specific exemption.

• Install Okta Verify exclusively in the work profile when using an Android work profile. Installing the application in both personal and work profiles causes device probing to fail, preventing Okta from recognizing the device as managed.