Okta Production – Release 2016.33 Skip to main content
https://support.okta.com/help/oktaarticledetailpage?childcateg=&id=ka0f0000000u80pkas&source=documentation&refurl=http%3a%2f%2fsupport.okta.com%2fhelp%2fdocumentation%2fknowledge_article%2fokta-production-release-2016-33
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 Production – Release 2016.33
Published: Aug 23, 2016   -   Updated: Jun 22, 2018

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

The following is available for all organizations with release 2016.33.

Integration Enhancement: We have improved Service Now Login URL logic to be more robust to prevent failed API connections.

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:

  • FloQast (OKTA-97522)

  • PostBeyond (OKTA-97523)

  • TrackWise by Sparta Systems
    (OKTA-76814)

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

  • Kindling (OKTA-98276)

  • Reflexis (OKTA-98278)

  • Netsimplicity Meeting Manager
    (OKTA-98419)

  • Lanyon StarCite (OKTA-98422)

  • Acuity Management Solutions
    (OKTA-98443)

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-90195 – The Okta On-Boarding screen failed to appear for Active Directory-mastered users accessing Okta through an SP-initiated connection (New Okta Sign In Experience).
  • OKTA-91079 – Okta Profile Master didn't reactivate users for Salesforce.
  • OKTA-91134 – Adding the Office 365 app failed under some circumstances.
  • OKTA-91151 – App names containing an ampersand were incorrectly displayed on the Okta Sign In page (old Sign In flow).
  • OKTA-94144 – The RightNow CX app set deprovisioned users to Permanently Disabled instead of Disabled.
  • OKTA-94145 – Mapping the postalAddress attribute from Active Directory (AD) to Okta failed.
  • OKTA-95902 – Increased the limit for AD groups with duplicate names when filtering group membership rules in Okta.
  • OKTA-96437 – Matching against attributes that exceed the allowed length of any app user attribute failed without an appropriate message, and the failure wasn't logged.
  • OKTA-96954 – The mobilePhone attribute was not pushed from Okta to the Jive app.
  • OKTA-96956 – The Okta Active Directory Password Sync agent returned a 404 error (New Okta Sign In Experience).
  • OKTA-97391 – Queries on old events in our new System Log (Early Access) resulted in an error.
  • OKTA-97515 – The initial setup flow for Voice Call MFA failed to render a Received Code field.
  • OKTA-98625H – Fixed an issue involving incorrect expiration of password recovery tokens.
  • OKTA-98717H – Pushing profile updates to Salesforce for users that are not members of a public group failed when support for public groups and feature licenses was enabled for the users in Okta.

App Integrations Fixes

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

  • Envoy (OKTA-98214)

  • GuideStar (OKTA-97893)

  • Purolator (OKTA-97793)

  • Sugar CRM (OKTA-98264)