Okta Production – Release 2016.38 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.38
Published: Sep 27, 2016   -   Updated: Jun 22, 2018

Okta Production Release 2016.38 began deployment on September 26. 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.38.

  • Okta updates the attributes of Okta Mobility Management (OMM) enrolled devices more frequently. This feature is now Generally Available (GA) for all orgs. For details, see Configuring Okta Mobility Management.

  • The App Settings modal now displays admin-assigned usernames. Displaying the username makes it easier for end users to install the mobile version of an app on their mobile devices.

    User-added image

Agent Updates

  • The Okta Java LDAP Agent version 5.3.7 is now available to Early Access (EA) users. This release provides internal logging improvements. For the version history, see Java LDAP Agent Version History.

  • The Okta On-Premises MFA Agent version 1.3.3 is now available to EA users. This release fixes an issue that prevented users from installing the agent in environments in which internet access is available only through a proxy server. For the version history, see On-Premises MFA Agent Version History.

To obtain these EA releases, contact Okta Support.

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:

  • Employers Mutual EMpower

  • GFS Canada (OKTA-99209)

  • IBM Bluemix (OKTA-100138)

  • SecurePay (OKTA-99014)

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

  • AlertMedia (OKTA-99311)

  • BuildingOS (OKTA-99875)

  • iiPay GPMS (OKTA-98876)

We've implemented SAML for the following Community Created applications:

  • MobileIron (OKTA-97952)

  • Netskope (OKTA-94216)

  • Youforce (OKTA-98311)

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

  • Microsoft Office 365

  • Mimecast Personal Portal v2

  • TrackWise by Sparta Systems

​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-84084 – The most-recently verified factor was not set as the default MFA option in orgs with the New Okta Sign-In Experience enabled.
  • OKTA-94685 – Workday-mastered user activations failed to automatically confirm and activate new users.
  • OKTA-95887 – The Suggest a Feature link at the bottom of the Admin console pointed to the wrong page.
  • OKTA-99348 – Changing email notification settings failed for Application Administrators in some orgs.
  • OKTA-99899 – Assigning an app to a very large group failed for some group members.
  • OKTA-100035 – Group membership rules did not trigger specified updates after user imports or updates. 
  • OKTA-100077 – The Application Access report did not run for some orgs.
  • OKTA-100133 – Provisioning the Netsuite app failed under certain circumstances.
  • OKTA-100191 – The advanced search in System Log 2.0 (EA) did not function for a certain field.
  • OKTA-100316 – Admins were unable to clear iPhone passcodes from the Devices page of the Okta Admin dashboard.
  • OKTA-100528 – Admins were unable to use the scroll bar or keyboard arrow keys to see groups specified in the Add Person modal.
  • OKTA-100632 – Duo setup for a U2F token failed when any existing MFA factor was already configured.
  • OKTA-102102H – SP-initiated Inbound SAML log-in flows failed under certain circumstances.

App Integrations Fixes

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

  • Bluemoon Software (OKTA-101231)

  • Box (OKTA-87381)

  • DoubleClick for Advertisers

  • K1000 Administrator Interface

  • K1000 Service Center

  • Microsoft Online Services
    Admin (OKTA-101063)

  • SAP BusinessObjects

  • Wells Fargo (OKTA-99074)