Okta Verify Release Notes

Okta Verify 4.2.0 for Android began deployment on September 5, 2018 and is available from the Google Play Store.

This release includes the following:

• When enrolling a device, new Okta Verify users are now prompted to grant the camera permission for QR codes to be scanned successfully.

• Push notifications that have expired after 5 minutes of inactivity no longer persist and are now removed silently.

Okta Verify 4.0.1 for Android began deployment on August 15, 2018 and is available from the Google Play Store.

This release includes the following:

• Early Access: Added support for admins to require user data storage in the Android hardware-backed keystore. This feature improves user security based on the Federal Identity, Credential, and Access Management (FICAM) architecture. For information on how to enable this feature, refer to the section Hardware Key Storage on Android Devices in Okta Verify.

Okta Verify 3.12.0 for Android began deployment on June 12, 2018 and is available from the Google Play Store.

This release includes the following:

• OKTA-167166 - Verification request notifications that are approved from a locked device no longer redirect to the challenge screen. For more information about verification request notifications, refer to Using Okta Verify.

Okta Verify 3.10.0 for Android began deployment on April 17, 2018 and is available from the Google Play Store.

This release includes the following:

• Adds support for Okta's Custom URL DomainA domain is an attribute of an Okta organization. Okta uses a fully-qualified domain name, meaning it always includes the top-level domain (.com, .eu, etc.), but does not include the protocol (https). feature, scheduled for Early Access availability in early May.

Okta Verify 3.8.0 for Android began deployment on February 8, 2018 and is available from the Google Play Store.

This release includes the following bug fixes:

• OKTA-139288/147690 – When signing in to Okta, some users received a second in-app MFA challenge after completing the initial challenge.
• OKTA -142172 – When tapping separate push notifications to sign in to separate Okta orgs, access to the first orgThe Okta container that represents a real-world organization. succeeded, but access to subsequent orgs did not.
• OKTA-146460 – Some text in the Okta Verify MFA push notification for Android was incorrect.
• OKTA-151330 – Mobile device users were able to approve or deny Okta Verify MFA challenges from locked screens.
• OKTA-151596 – After tapping Accept in Okta Verify to sign in to Okta, the authentication flow became stuck on the loading page.

Okta Verify 3.6.0 for Android began deployment on December 12, 2017 and is available from the Google Play Store.

This release includes the following bug fix:

Bug Fix:

• OKTA-147690 – When signing in to Okta, some users received a second in-app MFA challenge after completing the initial challenge.

Okta Verify 3.2.1 for Android began deployment on November 6, 2017 and is available from the Google Play Store.

This release includes the following bug fix:

• OKTA-117445 – After receiving a push authentication request, attempting to open the app instead of tapping the notification action buttons sometimes caused the app to quit unexpectedly.

Okta Verify 3.2.0 for Android began deployment on October 23, 2017 and is available from the Google Play Store.

This release includes the following bug fix:

• OKTA-142820 – Under rare circumstances, the app became inoperable immediately after it was launched.

Okta Verify 3.0.0 for Android began deployment on September 25, 2017 and is available from the Google Play Store.

This release includes performance and UI enhancements, as well as the following features and improvements:

• Okta Verify now supports multiple accounts, allowing you to use the app to authenticate into multiple organizations. Screenshots

  

• 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.

Okta Verify 2.8.0 for Android was released on November 2, 2016, and is available from the Google Play Store.

Okta Verify now honors the language set on your device.

Bug Fixes

• OKTA-96682 - The Okta Verify app crashed after the splash screen appeared.
• OKTA-78777 - Okta Verify with Push failed to allow the device to communicate with the server.

Okta Verify 3.8.0 for iOS began deployment on March 19, 2017 and is available from the Apple App Store.

Enhancement

The instructions available through the information icon are now provided in all Okta-supported languages.

Bug Fix

This release includes the following bug fix:

• OKTA-150333 - Okta Verify for iOS did not fill the entire screen on iPhone X devices.

Okta Verify 3.6.0 for iOS began deployment November 8, 2017 and is now available from the Apple App Store.

This release includes the following enhancements and bug fixes:

Enhancements:

• Okta Verify now supports localization into Turkish, Polish, Indonesian, and Malay.
• 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:

• OKTA-140272 - Attempts to approve push authentication requests failed if the user had enrolled in Okta Verify through SMS or email, rather than the QR code.

Okta Verify 3.4.0 for iOS was released March 29, 2017 and is now available from the Apple App Store.

This release included general performance enhancements and bug fixes, as well as:

New Feature

We added localization support for 24 languages.

Bug Fixes

• OKTA-111605 - Fixed an issue in which certain users did not receive push challenges when the app was in the foreground.

Okta Verify 3.0.0 for iOS was released on November 1, 2016 and is now available from the Apple App Store.

This release includes the following:

• A cleaner end user experience with a streamlined TouchID design.
• Enhanced security, allowing view of the one-time passcode (OTP) only after a successful TouchID or PIN authentication.

• Ability to authenticate multiple accounts and organizations, including accounts outside of Okta.Screenshot



• Convenient, in-app ability to enable camera access for Okta Verify. Screenshot