Okta Preview Release 2016.26 began deployment on June 29. 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.
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.
Platform Release Notes
Changes to the platform for this release are published in the Platform Release Notes on developer.okta.com.
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.
Unless otherwise noted, these features are available for all organizations with release 2016.26.
Incremental Features Summary
There are no incremental features to announce this week.
We have upgraded the Okta JIRA Authenticator to version 2.0.2. This release fixes an issue where the JIRA On-Premise app 7.1.2 failed to redirect users to Okta for authentication. For installation and configuration instructions, see Using the JIRA On-Premises SAML App. To obtain the latest JIRA Authenticator, visit the Okta Downloads page. For the toolkit version history, see Current JIRA JAR Version History.
Browser Plugin Updates
For plugin version history, see Browser Plugin Version History.
On July 1, 2016 Okta will discontinue support for Microsoft IE 9 as well as all versions of Compatibility View that represent IE9. After that date, Okta Support will no longer investigate issues related to IE9. For more information about supported browsers, see Platforms, Browser, and OS Support.
We've implemented SAML for the following Okta Verified applications:
We've implemented SWA for the following Okta Verified applications:
Bug numbers ending with an H are hotfixes. Hotfixes are generally deployed after the initial release.
The following issues are fixed:
App Integrations Fixes
The following SWA apps were not working correctly and are now fixed:
The following SAML app was not working correctly and is now fixed: