Okta Mobile – Release 2.14.0 for Android Skip to main content
https://support.okta.com/help/oktaarticledetailpage?childcateg=&id=ka02a000000xaacsak&source=documentation&refurl=http%3a%2f%2fsupport.okta.com%2fhelp%2fdocumentation%2fknowledge_article%2fokta-mobile-release-2-14-0-for-android
How satisfied are you with the Okta Help Center?
Thank you for your feedback!
How satisfied are you with the Okta Help Center?
1
2
3
4
5
Very Dissatisfied
Very satisfied
Enter content less than 200 characters.
Okta Mobile – Release 2.14.0 for Android
Published: Nov 30, 2016   -   Updated: Jun 22, 2018

The following Okta Mobile update began deployment on November 30 and is available from the Google Play Store this week.

Okta is pleased to announce the release of Okta Mobile 2.14.0 for Android.

This release includes general performance improvements, a known issue, and the following bug fixes:

Bug Fixes

The following issues are fixed:

  • OKTA-102515 – Changing the SSID name of an existing WiFi profile in Okta via Devices > WiFi didn't remove that WiFi profile from Android 6.0.1 SAFE devices, and such devices were still able to connect to the network under the old SSID name.

  • OKTA-102867 – Authenticating to the CalPERS SWA app failed for Okta Mobile for Android users.

  • OKTA-103593 – Clicking a native application in the Okta Mobile app opened the wrong app.

  • OKTA-103803 – If multiple certificates were uploaded and the first certificate (top-most in the list) was invalid (corrupted or expired), Android devices could not connect to the WiFi network.

  • OKTA-104026 – Changing the Security type from WPA/WPA2 Enterprise to either WPA2 Personal or WEP broke the WiFi configuration on Okta Mobile for Android on AfW devices.

  • OKTA-104027 – Instead of replacing the existing WiFi profile as expected, changing the Security type of a WiFi profile installed a new WiFi profile on AfW devices running Okta Mobile for Android

  • OKTA-104045 – Authenticating to the AdTech US SWA app failed for Okta Mobile for Android users.

  • OKTA-105408 – In orgs with the updated WiFi profiles feature (Early Access) enabled, if custom CA certificates were added to the WiFi configuration, Android users could not connect to the assigned WiFi network unless they selected unspecified for the CA certificate type in WiFi settings on their device.

  • OKTA-93260, OKTA-95287, OKTA-99046, OKTA-102978, OKTA-107231 – Internal improvements.

Known Issue – Deleting certificates

Note: This and other known issues are detailed in the topic WiFi Profiles.

In WiFi profiles configured with the security type WPA/WPA2 Enterprise, deleting a certificate in Okta has different results depending on the type of device:

  • Native Android – Google does not support the ability for Okta to delete certificates from Native Android devices. 
  • Samsung SAFE – Deleting certificates from Okta does not delete certificates from Samsung SAFE devices running Okta Mobile version 2.14.0 or earlier. Okta is working toward removing this limitation for Samsung SAFE devices in the next release of Okta Mobile for Android.
  • AfW – If you delete some but not all certificates from Okta, those certificates are deleted from AfW devices. However, if you delete all installed certificates from Okta, none are deleted from AfW devices. Okta is working toward removing this limitation for AfW devices in the next release of Okta Mobile for Android.