Okta Production Release 2016.21 began deployment on May 31. 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.
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.
New Product FeaturesUnless otherwise noted, these features are available for all preview organizations with this release.
New Platform FeaturesNote: You can find platform documentation and other developer resources at http://developer.okta.com.
WantAuthnRequestsSign Default Value
The WantAuthnRequestsSigned element in the SAML metadata returned from the Apps API has a default value of false as Okta does not require that AuthN requests be signed. A sample response showing this element is available in the response section in Preview SAML Metadata for Application.
Incremental Features Summary
The following table summarizes features that are enabled incrementally. Links in this table go to the release notes in which the feature was initially announced. After the feature is fully released, it is no longer tracked in this table. For release history of all features, see Features by Release.
Vendor-built provisioning is Okta Verified for the following application:
We've implemented SAML for the following Okta Verified applications:
We've implemented SAML for the following Community Created applications:
We've implemented SWA for the following Okta Verified applications:
We've added the following Mobile applications for use with Okta Mobility Management (OMM):
Bug numbers ending with an H are hotfixes. Hotfixes are generally deployed after the initial release.
Product Bug Fixes
The following issues are fixed:
App Integrations Fixed
The following SWA apps were not working correctly and are now fixed: