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

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.

New Product Features​

Unless otherwise noted, these features are available for all preview organizations with this release.
  • We have improved the user experience for our latest Microsoft Office 365 integration:

    • In order to provide for a more seamless implementation, the labels associated with each of the Office 365 provisioning types have been simplified.

    • Tooltips explain exactly what is synchronized, such as user attributes.

    • We have provided an in-product link to our Microsoft Office Deployment Guide.

    User-added image

    For more details, see Okta Enhancements with Microsoft Office 365 Integration.

    Availability: This  feature is available to all orgs in release 2016.21.

  • Certificates with a SHA256 signature are supported for SAML 2.0 applications with Okta. You can create new integrations that use SHA256 certificates and update existing integrations from SHA1 certificates to SHA256 certificates. For more information and detailed instructions, see Using a SHA256 Certificate with SAML 2.0 Apps.

    Availability: This is an Early Access (EA) feature; contact Okta Support to enable it.

  • For orgs with an Active Directory integration, import confirmation emails now include instance names. This makes it easier to identify specific instances in orgs with multiple instances.

    User-added image

    Availability: This  feature is available to all orgs in release 2016.21.

  • Good news for users of the SharePoint (On-Premises) app! Your custom user profile mappings are now preserved when Okta updates default mapping.

    Availability: This  feature is available to all orgs in release 2016.21.

New Platform Features

Note: 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.

FeaturePreview
New Orgs
Production
New Orgs
Preview
Existing Orgs
Production
Existing Orgs
New Okta Sign-in Experience2016.192016.192016.19
Workday Import Performance Improvement 2016.182016.182016.18 (5/9)2016.20-2016.22

Agent Updates

Application Updates

Integrations

Vendor-built provisioning is Okta Verified for the following application:

  • OrgWiki

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

  • Blissbook (OKTA-88103)

  • HackerRank For Work (OKTA-85594)

  • Kanjoya (OKTA-87185)

  • SenderGen (OKTA-89606)

  • TOPdesk 6 (OKTA-89604)

We've implemented SAML for the following Community Created applications:

  • Staples Advantage (OKTA-85459)

  • CoderPad SAML (OKTA-87686)

We've implemented SWA for the following Okta Verified applications:

  • Clari (OKTA-83069)

  • Foodsby (OKTA-86327)

  • Ohmygreen (OKTA-89886)

  • Qzzr (OKTA-90159)

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

  • LucidChart (OKTA-83888)

  • LucidChart (OKTA-83888)

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-75234 – Changes to the Device page did not dynamically update when a device was deprovisioned. The page now refreshes automatically.

  • OKTA-84714 – An app-specific sign on policy sometimes caused an authentication loop in the password and MFA sign on process.

  • OKTA-88470 – In orgs with the new Okta sign in experience enabled, end users attempting to sign in to an unassigned app with SP-initiated SAML were prompted to sign in to Okta a second time. 

  • OKTA-90526H – Generating paginated custom reports in Workday resulted in deactivating Pre-Start interval users.

  • OKTA-90654H – The Okta Profile Master function failed to reorder even after a new priority order was requested.  

App Integrations Fixed

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

  • ADP Run (OKTA-90026)

  • Cover-More Travel Insurance (AU) (OKTA-89341)

  • Diversified (OKTA-89258)

  • Geo Trust TrueFlex Enterprise Security
    Center (OKTA-89794)

  • Gliffy (OKTA-89791)

  • Google Analytics (OKTA-89520)

  • Lucernex IWMS (OKTA-89796)

  • My T-Mobile (OKTA-89795)

  • Navia Benefit Solution (Employer Portal) (OKTA-90240)

  • Navia Benefit Solution (Participant Portal) (OKTA-90241)

  • The Foundry (OKTA-89969)

  • WebEx Premium (OKTA-83747)

Post a Comment