Okta Preview Sandbox – Release 2016.36 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.36
Published: Sep 7, 2016   -   Updated: Jun 22, 2018

Okta Preview Release 2016.36 began deployment on September 8. 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.36.

  • With the exception of Czech and Ukrainian languages, we have promoted all supported languages that were formerly in beta format to General Availability (GA). You can select the default language preference for your entire org, and your end users can select a different language preference for their own experience. The end user's preference overrides the language set for the org. For more information, see Setting Language Preferences.

  • We've streamlined and optimized the Universal Directory (UD) Profile Editor! This new UD Profile Editor is now GA and has a cleaner look and provides quicker access to what you use most in UD. For details, see A New Look for Profile Editor.
  • System Log reports now include the names of updated app user properties.

Agent Updates

We have released Okta IWA Agent version 1.10.0. for Early Access (EA) users. With this release, SSO IWA log-in flows now display the org's logo if configured in Settings > Appearance > Organization Logo.

User-added image

To obtain this EA version, contact Okta Support. For version history, see IWA Web App 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.

Application Updates

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

  • JAMF Software Server (JSS)

  • Looop (OKTA-93451)

  • MuleSoft - Anypoint Platform

  • Octiv (OKTA-99742)

  • Reprints Desk (OKTA-98663)

  • Teamable (OKTA-99510)

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

  • Globe Telecom (OKTA-98561)


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-90799 – Okta System Logs reported incorrect IP addresses. 
  • OKTA-92338 – During password reset, the New Okta Sign In flow failed to display text describing password complexity requirements for Okta end users. 
  • OKTA-95411 – Some UD attributes were not populated for some users.
  • OKTA-97028 – The Okta custom portal login forced a second-session sign-on challenge, even after the Remember Me option was selected.
  • OKTA-98575 – SP-initiated login flows to SAML apps configured to require MFA failed in orgs with the New Okta Sign In Experience enabled.
  • OKTA-98768 – Usernames and passwords longer than 38 characters did not display completely in tooltips in orgs with the New Okta Sign In Experience enabled.
  • OKTA-98773 – The redesigned Edit Assignment window was not available to all users.
  • OKTA-99641 – The Duo security page for MFA did not display correctly.
  • OKTA-99753 – The RightNow CX app did not open after SAML authentication.
  • OKTA-99874 – Deprovisioning users from the Litmos app in bulk failed under certain circumstances.
  • OKTA-100318 – The Tombstone function failed for some users. 

App Integrations Fixes

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

  • Aetna Health Insurance (OKTA-99995)

  • AnyPerk (OKTA-99689)

  • Autodesk 360 (OKTA-100235)

  • Chase Paymentech (OKTA-97315)

  • Gaggle (OKTA-97718)

  • IMS Health (OKTA-99644)

  • NOW - NetApp (OKTA-100292)

  • Rakuten Affiliate Network

  • RingCentral (OKTA-99637)

  • Shopify (OKTA-99064)

  • Walmart (OKTA-99816)

The following SAML app was not working correctly and is now fixed:

  • TinderBox (OKTA-98894)