Okta Production – Release 2016.32 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 Production – Release 2016.32
Published: Aug 16, 2016   -   Updated: Jun 22, 2018

Okta Production Release 2016.32 began deployment on August 15. 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. 

Important Notice for AD Integrations Using Federated Profiles

If your Okta Active Directory (AD) integration uses Federated Profiles, you should update to the latest GA version of the Okta AD agent. Beginning April 21, 2016, Okta automatically migrated all orgs that use the Federated Profiles option to the Okta enhanced AD integration, which requires agent version 3.0.8 or higher. If your Okta AD agent is earlier than version 3.0.8, following the migration your organization may experience inconsistent behavior, including loss of groups and group memberships.

To identify orgs running Federated Profiles, see Determining Your AD Integration Type.

For download and installation instructions, see Installing and Configuring the Active Directory Agent.

Note: If you run multiple Okta AD agents, upgrade all agents on your domain servers to the same version. Running different versions of the AD agent can cause all of them to function at the level of your oldest agent.

What's New

Unless otherwise noted, these features are available for all organizations with release 2016.32.

  • We've streamlined and optimized the Universal Directory (UD) Profile Editor! This Early Access (EA) experience has a cleaner look and provides quicker access to what you use most in UD. For details, see A New Look for Profile Editor (Early Access).

  • A notification now displays near the top of your Okta Admin Dashboard if you are using Okta in an unsupported browser.

Agent Update

The Okta Java LDAP Agent version 5.3.6 is now available to EA users. This release fixes an error that occurred when creating users in LDAP. For the version history, see Java LDAP Agent Version History.

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.

Discontinued Support

Okta has discontinued support for OneDrive for Business. Users of the app are now prompted to upgrade to OneDrive for Business Next Generation Sync Client. For more information, see Upgrading to OneDrive for Business Next Generation Sync Client.

Application Updates

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

  • COMPAS Technology (OKTA-94002)

  • Epromo - E-Store (OKTA-92749)

  • Hosted Graphite (OKTA-97158)

  • Wizergos (OKTA-95497)

We've added the following Mobile application for use with Okta Mobility Management (OMM):

  • Code42 CrashPlan (PROe) (OKTA-95901)


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

  • BriefingSource by EchoVision, LLC

  • CloudPay (OKTA-97691)

  • Good AppCentral (OKTA-97781)

  • Serraview (OKTA-97359)

  • WebMD Health Services

Bug Fixes

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

Product Bug Fixes

The following issues are fixed:

  • OKTA-86386 – The Oracle Agile PLM app was unresponsive for Internet Explorer 11 users.
  • OKTA-92780 – The Okta plugin displayed the new password banner and the one-click sign-in banner in the wrong context when using the JotForm app.
  • OKTA-92795 – Attempts to configure SMS occasionally failed, leaving the user in the setup stage of the Extra Verification dialog.
  • OKTA-93027 – Group Push to the Jive app failed if the group name contained either a "/" or a "\".
  • OKTA-96062 – The wrong placeholder text appeared in the Username and Password fields on the Okta Sign In page.
  • OKTA-96524 – The View Log link on the Roadblock and Task pages did not link to our new EA System Log (when enabled).

App Integrations Fixes

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

  • HipChat (OKTA-96799)

  • Unity Ads (OKTA-97006)