Okta Preview Sandbox – Release 2016.37 Skip to main content
https://support.okta.com/help/oktaarticledetailpage?childcateg=&id=ka0f0000000u8dekak&source=documentation&refurl=http%3a%2f%2fsupport.okta.com%2fhelp%2fdocumentation%2fknowledge_article%2fokta-preview-sandbox-release-2016-37
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.
Average Rating:
Okta Preview Sandbox – Release 2016.37
Published: Sep 13, 2016   -   Updated: Sep 28, 2016

Okta Preview Release 2016.37 began deployment on September 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

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 Update

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

  • Mimecast Personal Portal V3 (OKTA-100167)

    ​We've implemented Provisioning for the following Partner-Built applications:

    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-94942 – Leaving the optional Workday attribute Degree_Name empty resulted in an error.
    • OKTA-99100 – Enrolling a user's phone number for MFA that was already enrolled caused an error.
    • OKTA-99573 – Attempts to generate a usage report for a specific group resulted in a blank CSV file.
    • OKTA-99751 – The Native App only label was misleading, as a native app and an SPA both can be specified when creating a new OIDC client application. The label now reads Native App.
    • OKTA-100030 – The scroll bar in the in the Add Administrator modal disappeared when assigning apps to an Application Administrator.
    • OKTA-100180 – When adding an Application Administrator and specifying apps, the auto-suggest feature failed if the app name contained certain non-alphanumeric characters.
    • OKTA-100405 – For AD Mastered users, not all the fields on the end-user Settings page were localized as specified.

    App Integrations Fixes

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

    • Invoca (Tapjoy) (OKTA-97613)

    • Sentry (OKTA-100521)

    • Ubiquity Retirement Login
      (OKTA-100725)

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

    • Mimecast - Admin (OKTA-94254)

     

    Post a Comment