Okta Preview Sandbox – Release 2016.22 Skip to main content
https://support.okta.com/help/oktaarticledetailpage?childcateg=&id=ka0f0000000mcfhka0&source=documentation&refurl=http%3a%2f%2fsupport.okta.com%2fhelp%2fdocumentation%2fknowledge_article%2fokta-preview-sandbox-release-2016-22
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.
Okta Preview Sandbox – Release 2016.22
Published: Jun 1, 2016   -   Updated: Jun 22, 2018
Okta Preview Release 2016.22 began deployment on June 1. 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 organizations with release 2016.22.
  • Functionality of the Tasks page is enhanced to allow admins to edit all fields in the app assignment screen when processing provisioning, activation, and validation feature tasks. For more information see About Your Administrator Dashboard.

    Availability: This feature is available in release 2016.22 preview for all organizations and in 2016.22 production for new organizations.

  • Use the OAuth tab to configure OAuth and OpenID Connect elements for your apps. Note: the Groups claim for an app is in the OpenID Connect ID Token panel of the OAuth tab. It was previously in the General tab.

  • The Box Provisioning Integration has been changed to use the new API authentication endpoints for compatibility with the new Box release. No customer action is required.

  • As part of the Android for Work setup flow, admins now need to Approve Okta Mobile’s permissions, as shown below. This allows users to receive Okta Mobile updates automatically. See the Android for Work Setup instructions.

    User-added image

  • Admins can now easily choose whether end-users who have successfully unlocked their Okta accounts can also be automatically unlocked in AD. For details, see Configuring Group Password Policies.

    User-added image

New Platform Features

More information about errors is returned from the following endpoints:

Note: You can find platform documentation and other developer resources at http://developer.okta.com.

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 Update

The Okta Java LDAP Agent version 5.3.5. is now available to Early Access (EA) users. This release provides additional diagnostic information for use by Okta engineering. For version history, see Java LDAP Agent Version History.

Application Updates

Integrations

The JIRA (Atlassian) application has been deprecated. Okta recommends that you upgrade to the JIRA Cloud app if you are on the cloud version of JIRA, or the JIRA On-premise app if you are on a JIRA server. All of the latest updates and new functionality will be added to these versions going forward.

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

  • Feedly (OKTA-89700)

  • Precision Digital Health
    - SUMMA (OKTA-87481)

  • Rollbar SAML (OKTA-90257)

  • TriNet (OKTA-89388)

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

  • Accredible (OKTA-90156)

  • AuctionGenius (OKTA-90162)

  • AutoCheck (OKTA-90743)

  • Best Buy For Business (OKTA-90746)

  • Cloudcraft (OKTA-90744)

  • CSI - WatchDOG Elite (OKTA-90183)

  • FileWave (OKTA-90747)

  • Index Exchange (OKTA-90176)

  • Justifacts (OKTA-88377)

  • Landmark Global - Mercury
    (OKTA-90634)

  • Level 3 Communications (OKTA-88996)

  • Multivista (OKTA-90164)

  • mySonitrol (OKTA-90160)

  • Nexudus (OKTA-90630)

  • NorthStar Alarm Services
    (OKTA-90742)

  • Pantheon (OKTA-90632)

  • Quorum (OKTA-90741)

  • RedRock Software (OKTA-90631)

  • theBiz (OKTA-90163)

  • TripleLift (OKTA-90178)

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

  • Chase Loan Manager (OKTA-88909)

  • Chrome Browser (OKTA-89656)

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-81458 – When the Licenses/Roles Management Only option was selected, some provisioning settings for the O365 app that should have been hidden were still available.
  • OKTA-86561 – Profile pushes to the Jive app removed attribute values modified outside of Okta.
  • OKTA-88519 – Some groups failed to push to the Jive app due to a parsing error.
  • OKTA-88523 – Imports from the BambooHR app failed after deprecation of the TLS 1.0 encryption protocol.
  • OKTA-89964 – New users could not complete the welcome screen with the new Early Access Okta sign-in experience enabled.
  • OKTA-90126 – A gray box appeared behind icons in the Add Rule dialog box on the Sign-on Policy page.
  • OKTA-90310 – If Attribute-level Mastering (ALM) is enabled with two profile masters, the profile mastery could not be changed. 

Platform Bug Fixes

The following issue is fixed:

  • OKTA-90514 – The Roles API did not allow the USER_ADMIN role to have a group scope.

App Integrations Fixed

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

  • Customer.io (OKTA-90685)

  • DocuSign (OKTA-81013)

  • Fluke Support (OKTA-88713)

  • GoFormz (OKTA-90103)

  • Salesforce Customer Portal
    (OKTA-82752)

  • TravelCube Pacific
    (OKTA-89294)