Okta Verify for Okta Identity Engine release notes
You can download the Okta Verify package for Android from these locations:
-
Okta Admin Console ( ). The updated package file is available approximately two weeks after the deployment date. See Distributing Okta Android apps outside the Google Play Store.
Version: 8.11.0
Deployment date: 2025-08-18
Release summary
- This release includes internal improvements and fixes.
You can download the Okta Verify package for iOS from these locations:
-
Okta Admin Console ( ).
Version: 9.48.0
Deployment date: 2025-08-18
Release summary
-
This release includes internal improvements and fixes.
-
Sometimes troubleshooting checks for Okta Verify Push notifications showed an unnecessary warning. (OKTA-982065)
You can download the Okta Verify package for macOS from these locations:
-
Okta Admin Console ( ).
Version: 9.48.0
Production deployment: 2025-08-14
Release summary
- This release includes internal improvements and fixes.
You can download the Okta Verify package for Windows from the Okta Admin Console ( ).
Version: 6.1.1
Preview deployment: 2025-08-19
Release summary
-
This release enhances the Desktop MFA feature on Windows to include an admin-assisted recovery path.
If a user is locked out of their Windows device, an admin can now issue a time-based recovery PIN. This grants the user temporary access to their computer without needing their primary MFA device, enabling them to resolve their authenticator issue and sign in successfully.
-
When the UseDirectAuth and PasswordlessAccessEnabled policies were both enabled for use with FIDO2 keys, new users who hadn't already signed in received three push notifications during their initial sign-in attempt. (OKTA-976811)
-
Users sometimes saw a login failed response instead of successful login when they canceled a FIDO2 assertion and immediately started a new one. (OKTA-838071)
-
In certain cases, a user could be prevented from signing in if they had no online or offline factors enrolled, even if the MaxLoginsWithoutEnrolledFactors policy maximum wasn't reached. (OKTA-837497)