Okta Mobile for Android release notes

Okta Mobile provides Single Sign-On (SSO) capability to all the apps on your Android device. As a companion app to the Okta Identity Management Service, Okta Mobile lets you sign in with your Okta credentials and have immediate access to all of your company's apps.

Okta Mobile for Android is available in the Google Play Store or as a direct download from the SettingsDownloads page in the Okta Admin Console.

For admins looking to download the APK files from the Admin Console for direct distribution to your users, see Distributing Okta Android apps outside the Google Play Store.

If you're looking for Okta Verify release notes, see Okta Verify for Okta Classic Engine release notes .

Version: 4.24.1

Deployment date: 2023-05-01

Release summary

  • This version includes internal improvements and fixes.

Version: 4.22.0

Deployment date: 2021-04-18

Release summary

Version: 4.21.0

Deployment date: 2021-11-01

Release summary

  • In environments where Google Play Store services aren't available, the Okta Mobile installation failed when admins downloaded and used installation software (APK files) from the Okta Admin Console (SettingsDownloads). (OKTA-429681)
  • Other internal fixes.

Version: 4.20.1

Deployment date: 2021-06-22

Release summary

  • This version includes several internal improvements and fixes.

Version: 4.19.0

Deployment date: 2021-04-19

Release summary

  • After admins set up a custom URL with CloudFlare, some end users received the error Unable to establish secure connection with Okta when using the custom URL in Okta Mobile for Android. (OKTA-361331)
  • Various internal fixes.

Version: 4.18.1

Deployment date: 2021-02-09

Release summary

  • This version includes several internal improvements.

Version 4.17.1

Deployment date: 2020-11-16

Release summary

  • This release fixed potential security vulnerabilities associated with the implementation of toasts. (OKTA-327529, OKTA-311107)

  • On Android devices, users can now test beta versions of Okta Mobile using Google Play. To start testing, open Okta Mobile and go to SettingsJoin beta.

    See Try new Android apps before they're officially released. (OKTA-342894)

  • Other internal improvements.

Version: 4.15.1

Deployment date: 2020-09-21

Release summary

  • Sometimes when opening apps from Okta Mobile on Android devices, users weren't prompted with a choice to select either the native app or the website. (OKTA-297673)

  • Version 4.15.1 is now available for administrators on the Downloads page.

    This is an alternative way to access Okta Mobile Android installation software (APK files) in locations where the Google Play Store and Google Services aren't available. For more information about downloadable Android installers, see Distributing Okta Android apps outside the Google Play Store.

  • Other internal improvements.

Version: 4.14.0

Deployment date: 2020-08-03

Release summary

  • Android device users were prompted for multifactor authentication (MFA) even when the Okta sign-on policy was configured to bypass MFA on known devices.

  • When users entered an incorrect URL, Okta Mobile failed instead of displaying an error message.

  • Version 4.14.0 is now available for administrators on the Downloads page.

    This is an alternative way to access Okta Mobile Android installation software (APK files) in locations where the Google Play Store and Google Services aren't available. For more information about downloadable Android installers, see Distributing Okta Android apps outside the Google Play Store.

  • Other internal improvements.

Version: 4.13.0

Deployment date: 2020-07-20

Release summary

  • After users signed in to Okta, they were prompted to authenticate with Okta Verify even if their devices weren't enrolled.

  • When signing in to Okta Mobile, entering an invalid domain URL generated a message that erroneously reported malicious activity.

  • Version 4.13.0 is now available for administrators on the Downloads page.

    This is an alternative way to access Okta Mobile Android installation software (APK files) in locations where the Google Play Store and Google Services aren't available. For more information about downloadable Android installers, see Distributing Okta Android apps outside the Google Play Store.

  • Other internal improvements.

Version: 4.12.0

Deployment date: 2020-07-06

Release summary

  • This version includes several internal improvements.

  • Version 4.12.0 is now available for administrators on the Downloads page.

    This is an alternative way to access Okta Mobile Android installation software (APK files) in locations where the Google Play Store and Google Services aren't available. For more information about downloadable Android installers, see Distributing Okta Android apps outside the Google Play Store.

Version: 4.11.0

Deployment date: 2020-06-22

Release summary

  • Users signing in to Okta from a known Android device received an MFA challenge although their org policy was configured not to prompt for MFA on known devices.

  • Version 4.11.0 is now available for administrators on the Downloads page.

    This is an alternative way to access Okta Mobile Android installation software (APK files) in locations where the Google Play Store and Google Services aren't available. For more information about downloadable Android installers, see Distributing Okta Android apps outside the Google Play Store.

  • Other internal improvements.

Version: 4.10.0

Deployment date: 2020-06-08

Release summary

This version includes several internal improvements.

Version: 4.9.0

Deployment date: 2020-05-20

Release summary

  • Sometimes users weren't automatically signed in to SAML apps.

  • Other internal improvements.

Version: 4.7.0

Deployment date: 2020-04-13

Release summary

  • Okta Mobile crashed when opening some native apps from within the Okta Mobile webview.
  • Other internal fixes.

Version: 4.6.1

Deployment date: 2020-03-26

Release summary

  • After users enrolled in a work profile, Okta Mobile was sometimes unresponsive at the verifying enrollment step.

  • Sometimes users weren't automatically signed in to SAML apps.

  • Internal fixes and enhancements.

Version: 4.5.1

Deployment date: December 11, 2019

Release summary

  • Internal fixes and enhancements.

  • Addresses an issue in 4.5.0 that caused Okta Mobile to crash when some users opened an app from within the Okta Mobile webview.

Version: 4.5.0

Deployment date: 2019-12-09

Release summary

This release fixes several internally found bugs.

Version: 4.3.2

Deployment date: November 19, 2019

Release summary

When opening version 4.3.1 of the Okta Mobile for Android app, end users were signed out of their account and shown the message "Detected possible malicious activity when establishing a secure connection to Okta."

Version: 4.3.1

Deployment date: 2019-11-06

Release summary

This release fixes several internally found bugs.

Version: 4.1.1

Deployment date: 2020-10-25

Release summary

This release fixes several internally found bugs.

Version: 4.1.0

Deployment date: 2019-10-04

Release summary

  • Okta Mobile Android icons are updated to be adaptive icons. Adaptive icons can display various shapes across different device models. See Adaptive icons.

  • This release fixes several internally found bugs.

Version: 4.0.0

Deployment date: 2019-09-30

Release summary

  • Device Trust flows timed out on Office 365 apps on Android 6.

  • End users were unable to sign in to Twitter through Okta Mobile on Android devices.

Version: 3.14.2

Deployment date: 2019-09-11

Release summary

  • To address changes introduced in Android 10, version 3.14.2 of Okta Mobile for Android notifies users to tap the screen to complete the OMM-Android Enterprise enrollment.

Version: 3.14.1

Deployment date: 2019-06-11

Release summary

  • Okta Mobile 3.14.0 crashed when Android 4.4 device users tried to satisfy an MFA challenge or access apps in Okta Mobile. (OKTA-232104)

Version: 3.14.0

Deployment date: 2019-06-10

Release summary

  • Accessibility enhancements such as improved support for screen readers.

  • Before the release of Okta Mobile 3.14 for Android, trying to access custom apps from the Okta Mobile-provided browser (WebView) failed. To increase compatibility with more apps, Okta Mobile for Android no longer conforms with Google's default behavior of blocking third-party cookies (in effect since Android 5.0). (OKTA-224158)

Version: 3.12.0

Deployment date: 2019-04-08

Release summary

  • Accessing SWA apps configured with per-app MFA failed from Okta Mobile for Android. (OKTA-195947)

Version: 3.10.1

Deployment date: 2019-02-06

Release summary

  • Using Okta Mobile 3.10.0 for Android to SSO into SAML apps on an HTTP endpoint failed. (OKTA-206552)

Version: 3.10.0

Deployment date: 2018-12-10

Release summary

  • This release fixes several internal bug fixes and provides minor UI improvements.

  • When trying to enroll in Okta Mobility Management, end users with Google Pixel devices (version 1 or 2) running Android Pie received a verification error and couldn't enroll their device. (OKTA-193448)

  • Beginning 20 December, 2018, version 3.10.0 became available on the Downloads page.

    This is an alternative way to access Okta Mobile Android installation software (APK files) in locations where the Google Play Store and Google Services aren't available. For more information about downloadable Android installers, see Distributing Okta Android apps outside the Google Play Store.

Version: 3.8.1

Deployment date: 2018-08-30

Release summary

  • Custom URL Domain: This feature allows you to customize your Okta org by replacing the Okta domain name with a custom URL domain name that you specify.
  • Enhanced Okta Mobile Security settings: Early Access customers can use new security settings available in the Admin console to manage PIN length and complexity.

This release includes the following bug fixes:

  • Internal bug fixes. (OKTA-139053, OKTA-173244)
  • Attempting to open new tabs or dialog boxes within apps launched from Okta Mobile for Android failed in some circumstances. (OKTA-164605)
  • When clicked from within Okta Mobile on Android, the link and button for uploading files to Box were inoperative. (OKTA-177397)
  • In orgs with Okta Mobility Management enabled, Okta Mobile reported an inaccurate serial number for some Android devices built by manufacturers such as Samsung. (OKTA-179615)

Version: 3.6.2

Deployment date: 2018-07-19

Release summary

  • For customers with G Suite, duplicate email accounts were configured in Gmail after Android users enrolled their device in OMM (work profile). (OKTA-131104)
  • In some circumstances, the option Use fingerprint to sign-in did not appear in Okta Mobile Settings. (OKTA-176999)

Version: 3.6.1

Deployment date: 2018-05-15

Release summary

Fixed an issue that prevented Okta Mobile from launching on OMM-enrolled Android 4.4 devices. (OKTA-171251)

Version: 3.6.0

Deployment date: 2018-05-09

Release summary

  • Okta Mobile Android device users enrolled in Okta Mobility Management could not access the Google Play store for Work after setting up the required device security, such as a passcode. (OKTA-156941)
  • AD-sourced Android device users running Okta Mobile 3.4.0 -3.4.2 could not enroll devices in Okta Mobility Management if Okta Mobile was stopped and then restarted. (OKTA-162378)

Version: 3.4.2

Deployment date: 2018-03-09

Release summary

  • Okta Mobile Android end users were restricted from enrolling in OMM even after the enrollment restrictions mobile policy was disabled for their user group. (OKTA-159835)

Version: 3.4.1

Deployment date: 2018-02-13

Release summary

Okta Mobile for Android now supports Transport Layer Security (TLS) 1.1 on Android 4.4 devices. As before, Okta supports TLS 1.2 on Android 5.0+ devices.

Version: 3.4.0

Deployment date: 2018-01-22

Release summary

  • Okta Mobile Android users could not finish signing documents with the DocuSign app. (OKTA-135379)
  • General performance enhancements.
  • Some Okta Mobile Android users could not sign in to Okta Mobile using Pin. (OKTA-145039)
  • Okta Mobile for Android displayed incorrect labels for Workplace Chat by Facebook and other apps. (OKTA-146445)
  • Provides general fixes and performance enhancements. (OKTA-150866)

Version: 3.2.0

Deployment date: 2017-10-03

Release summary

  • End users who have Android 6.0+ devices with fingerprint sensors can now unlock Okta Mobile with a fingerprint. To enable this feature, contact Okta Support.
  • When setting up an Android for Work profile during OMM enrollments of G Suite accounts, Play for Work enablement was either delayed or never completed. (OKTA-141135)
  • After authenticating into Okta Mobile with a PIN, the browser version of the Okta dashboard sometimes displayed instead of the mobile version. (OKTA-137277)

Version: 3.0.0

Deployment date: 2017-08-22

Release summary

  • Okta admins can now configure an Android for Work profile passcode policy in addition to or instead of a device passcode policy for their end users with Android 7.0+ devices.
  • End users now receive a notification if their device or work profile passcode does not comply with their group's mobile passcode policies.
  • For additional clarity and transparency, the legal information in Settings now includes separate menu items for Third Party Software Notices, our Privacy Policy, and our Terms and Conditions.

Bug Fixes

  • Samsung SAFE device users lost access to Microsoft Office 365 email from the native mail app when the EAS sign-on policy was updated. (OKTA-131502)
  • After tapping a SWA app, mobile device users were prompted to enter credentials instead of being authenticated automatically. (OKTA-134546)
  • A screen that informs users about their privacy during OMM enrollment was missing some clarifying text. (OKTA-135592)

Version: 2.18.1

Deployment date: 2017-06-16

Release summary

  • In some circumstances, credentials for SWA apps accessed within Okta Mobile were not saved. (OKTA-120766)
  • The message shown to Android users within Okta Mobile when their password expired did not specify that the password had to be reset from a browser. (OKTA-121915)
  • When users clicked an app in Okta Mobile, the prompts presenting different methods to open the app did not include buttons for selecting a method. (OKTA-124267)
  • Signing in to Okta Mobile failed for Android device users after they selected Duo MFA and accepted the Duo Push prompt. (OKTA-124291)
  • Attempting to open Google Play for Work within Okta Mobile (Android) failed after the admin changed the mobile device passcode policy, even after users reset their password to comply with the new policy. (OKTA-125252)

Version: 2.16.2

Deployment date: 2017-03-13

Release summary

  • After some users enrolled in Android for Work (AfW), Okta Mobile stopped working and AfW setup didn't complete properly. (OKTA-113005, OKTA-115086)