Okta Preview Sandbox – Release 2016.28 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.28
Published: Jul 12, 2016   -   Updated: Jun 22, 2018
Okta Preview Release 2016.28 began deployment on July 13. 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.28.

  • Like Super, Org, User, App, and Read-only admins, now Mobile admins can choose not to receive email notifications about locked user accounts. For more information, see Using the Okta Settings Page. For more about admin permissions, see Administrator Roles.

    User-added image

  • The ability to automatically release Google licenses when an Okta user is deprovisioned or deactivated is now Generally Available. This feature allows Google Apps elements to be centrally and granularly managed within Okta. For more details on this feature, see Managing Google Licenses.

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.

Browser Support

On July 1, 2016 Okta discontinued support for Microsoft IE 9 as well as all versions of Compatibility View that represent IE9. Okta Support will no longer investigate issues related to IE9. For more information about supported browsers, see Platforms, Browser, and OS Support.

Application Updates

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

  • Fidelity NetBenefits (OKTA-69476)

  • Skytap (OKTA-84195)

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

  • OKTA-94231 (7Geese)

  • OKTA-94482 (Aha!)

  • OKTA-94625 (Amazon Web Services)

  • OKTA-94486 (BMC Remedyforce SAML)

  • OKTA-94418 (BrightIdea)

  • OKTA-94438 (ClickTime)

  • OKTA-94416 (Gorilla Expense)

  • OKTA-94413 (GoToAssist
    (RemoteSupport/Service Desk/Monitoring))

  • OKTA-94478 (GoToTraining)

  • OKTA-94228 (LogMeIn)

  • OKTA-94233 (OpenVoice)

  • OKTA-94409 (ShopperTrak)

  • OKTA-94406 (Showpad)

  • OKTA-94432 (Simpplr)

  • OKTA-94480 (StatusPage)

  • OKTA-94411 (TOPdesk 6)

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-76352 – Provisioning failed in some editions of the Concur app when the Expense Group ID field was left empty.
  • OKTA-91433 – Samanage orgs without at least one group, and Samanage attributes that contained special characters, did not sync properly.
  • OKTA-92175 – The formatted address attribute for Facebook at Work was not recognized after Facebook’s API was updated.
  • OKTA-92433 – In cases where a logo wasn't associated with an uploaded hosted app, the Settings tab for that app was not displayed.
  • OKTA-93484 – The New Sign-on Experience RSA SecureID page failed to obfuscate the passcode entry text. 
  • OKTA-93577 – Workday users were deactivated in error following a full import in orgs in which admins changed custom reports and phone number mappings in the app.
  • OKTA-93821 – Provisioning users to the Pingboard app failed under certain circumstances.

App Integrations Fixes

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

  • Amazon Web Services (OKTA-93875)

  • Box (OKTA-94459)

  • Creditsafe (OKTA-94387)

  • Google AdWords (OKTA-94109)

  • T. Rowe Price (OKTA-94035)

  • WORK NUMBER (Employee)