Okta Preview Sandbox – Release 2016.51 Skip to main content
How satisfied are you with the Okta Help Center?
Thank you for your feedback!
How satisfied are you with the Okta Help Center?
Very Dissatisfied
Very satisfied
Enter content less than 200 characters.
Okta Preview Sandbox – Release 2016.51
Published: Dec 21, 2016   -   Updated: Jun 22, 2018

Okta Preview Release 2016.51 began deployment on December 21. For the latest information on our release schedule, see Current Release Status.

Check the version number at the bottom of your Okta Administrator page to see your current version. Clicking the version number takes you directly to the folder containing the release notes.

User-added image

Version numbers indicate the year and week of the year that releases are pushed to orgs. For example, release 2016.02 was pushed the second week of 2016. The week numbers follow the ISO Week Date convention. 

Special Announcements

Two Plugin Features to be Enabled for All Orgs in December 

Until now, not all Okta end users have seen the following Okta plugin features. These features will be enabled for all orgs starting this month:

  • Automatic App Login – This feature enables the Okta browser plugin to recognize the login fields of apps that users navigate to directly, without going through the Okta Dashboard. Users can log in to more apps automatically, without needing to enter credentials. 
  • Save Password Banner – This feature displays a banner that offers to save passwords for most of the standard online apps that they visit. For more about this feature, see Adding an App from the Browser Plugin.

Changes to Okta Support for Android Mobile Operating System

Okta Mobile and Okta Verify currently support Android versions 4.0.4 and earlier, but our support for these versions ends on January 16, 2017. After that date, Okta will only support version 4.4.x and higher. Android for Work (AfW) is supported on Android 5.1.1 and higher. For more information, see Okta Support for Mobile Operating System Versions.

Chromium Mandatory Certificate Transparency Policy Impact on Android Devices

Certificate Authorities (CAs) Symantec and GeoTrust have yet to implement the Chromium Certificate Transparency policy. This means that Android devices running on some versions of Chrome 53 and 54 might refuse to accept certificates from these CAs. For more information, see Known Issue: Impact of Chromium Mandatory Certificate Transparency policy on Android devices.

Apple iOS 10 Upgrade Impact on Okta Mobility Management Password Sync

Users who have upgraded to iOS 10 should note the following: If you’re using Okta Mobility Management (OMM) to configure Exchange ActiveSync (EAS) profiles, a known issue has been introduced that affects OMM’s ability to perform Password Sync for EAS profile updates on iOS devices. For details and workarounds, see Known Issue: iOS10 upgrade impacts Okta Mobility Management (OMM) Password Sync.

What's New

We have enhanced the functionality of the User Admin role (Early Access) as follows:

  • User Admins can now use Manage People functionality on the Groups page.

  • User Admins can now remove people from groups that they manage.

  • User Admins can no longer view the Directory Integrations page.

This is an EA feature; to enable it contact Okta Support. For more information, see The User Admin Role (Early Access).

Platform Release Notes

Changes to the platform for this release are published in the Platform Release Notes on http://developer.okta.com.

Incremental Features Summary

There are no incremental features to announce this week.

Application Updates

We've implemented SWA for the following Okta Verified applications:

  • Cook County Illinois

  • IBM Workspace (OKTA-108330)

  • NGS Connex (OKTA-109435)

We've implemented SAML for the following Okta Verified applications:

  • Brandfolder (OKTA-94408)

  • kCura Relativity (OKTA-108994)

  • KiSSFLOW (OKTA-90145)

  • Konverse (OKTA-109697)

  • Skeddly (OKTA-107243)

  • Spotinst (OKTA-109966)

We've changed Signature/Digest algorithms from SHA1 to SHA256 for the following SAML apps:

  • Syncplicity (OKTA-110529)

  • Wombat Security Technologies

Bug Fixes

Bug numbers ending with an H are hotfixes. Hotfixes are typically deployed after the initial release.

Product Bug Fixes

The following issues are fixed:

  • OKTA-68970 – The Call Me button displayed incorrectly on the Duo Authentication screen.
  • OKTA-106667 – The new System Log (EA) did not display API rate limiting errors.
  • OKTA-107190 – Mapping the attribute ms-Exch-Mailbox-Guid to Okta caused imports of new users from Active Directory (AD) to fail.
  • OKTA-107251 – The MSRtcSipPrimaryUserAddress attribute type incorrectly changed when the provisioning type changed.
  • OKTA-108094 – Reactivation of deleted users in Dropbox failed.
  • OKTA-108100 – The documentation describing several iframe functions for customizing end-user Home pages contained some errors.
  • OKTA-108562 – After editing scopes in the General Settings tab for a single-page app (SPA; OIDC) and saving changes, navigating to another area of Okta deselected all scopes. 
  • OKTA-108926 – When the fromURI parameter contained /oauth2/ and a security question had not been set up, redirects failed.
  • OKTA-109130 – Okta Mobile for iOS users were unable to install the SalesForce app from the Okta App Store.
  • OKTA-109874 – SCIM connector configurations could not be updated for app instances that used the authentication type http Header.
  • OKTA-110453 – The latest update to the mobile policy feature incorrectly allowed admins to edit Default policy rules.
  • OKTA-110792 – Orgs configured to use the red-bright theme in Settings > Appearance were reverted to the default theme.

App Integrations Fixes

The following SWA apps were not working correctly and are now fixed:

  • Accela (Civic Platform)

  • Klaviyo (OKTA-110451)

  • MetLife MyBenefits (OKTA-108626)

  • Optum Health Financial

  • SlideShare (OKTA-110106)

  • SunTrust - Enterprise Spend
    Platform (OKTA-110362)