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

Okta Preview Sandbox (oktapreview.com) features from 2016.46 and 2016.47 have been combined and pushed to Production (okta.com) 2016.47. This deployment began on November 28. 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. 

Special Announcements

Apple iOS 10 Upgrade Impact on Okta Mobility Management Password Sync

If you’re using Okta Mobility Management (OMM) to configure Exchange ActiveSync (EAS) profiles, a known issue has been introduced that affects OMM’s ability to perform Password Sync for EAS profile updates on iOS devices. For details and workarounds, see Known Issue: iOS10 upgrade impacts Okta Mobility Management (OMM) Password Sync.

Okta Mobile Connect

The latest updates to Box (v 3.8.9) and Workday (v 2016.41.156.401708) mobile apps have allowed for compatibility with Okta Mobile Connect (OMC), an Okta flow that enables SSO for native mobile apps. As a result, Okta will re-enable OMC, for Box and Workday only, on November 28th. Other apps previously using OMC will remain disabled until vendors fix the existing issues related to Apple iOS 10 compatibility. For details and a workaround for end users who do not upgrade to the latest versions, see Known Issue: Apple iOS update causes failure in Okta Mobile Connect.

Deprecation Announcement for iOS 8

Okta support for iOS 8 ended on November 13, 2016. Existing end users are not affected. Users attempting new installations on iOS 8 will see a notice stating that their OS version is no longer supported. After November 13th, Okta will chiefly support iOS versions 9.x and 10.x. For details on this version and our mobile support policy, see Okta Mobile and Okta Verify Supported Versions.

We're Auto-Enabling the New Okta Sign-In Experience

The New Okta Sign-In Experience currently is available to all orgs which have chosen to enable it in Settings > Appearance > Sign-In Configuration. If you have not done so already, we recommend that you enable the feature now to let your users become familiar with it. Beginning November 15, 2016 Okta began enabling the feature automatically for all new production orgs and all new and existing preview orgs and that have not enabled it already.

User-added image

The New Okta Sign-In Experience has been Generally Available (GA) for the past two quarters and is currently in use by hundreds of Okta customers. For more information about this feature, see New Okta Sign-In Experience.

What's New

Unless otherwise noted, these features are available for all organizations with release 2016.47.

  • An enhanced app assignment screen is available as an Early Access (EA) feature. You can toggle between people and groups on the same screen, view an error message when displaying people if an assignment cannot be completed, and select Assign to people or Assign to groups from the Assign button, as shown below.

    User-added image

    This is an EA feature; contact Okta Support to enable it.

  • Okta Verify Auto-Push makes Multifactor Authentication (MFA) even easier. Now, when end users land on the MFA challenge page (with Okta Verify with Push enabled), the challenge is sent automatically with no need to click Send Push. To set up this feature, end users select Send Push Automatically on the authentication screen. For more information, see Okta Verify with Push Authentication.

    User-added image

    This is an EA feature; contact Okta Support to enable it.

  • Support for the Indonesian language for the end user experience is now available to all customers in Beta format. You can select the default language preference for your entire org, and your end users can select a different language preference for their own experience. The end user's preference overrides the language set for the org. For more information, see Setting Language Preferences.

  • Provisioning for the Slack app now uses OAuth authentication and test tokens have been phased out. Existing app instances have been migrated and will continue to function. Creating new instances or re-authenticating old ones will require the admin to go through the OAuth authorization flow instead of a test token.

  • We have improved the messages displayed when setting up an OAuth app instance. After credential authorization, the user either sees an appropriate error message if authorization fails, or Re-authenticate with . . . if authorization succeeds.

  • The legacyEventType field in our new System Log (EA) is now searchable. Note that this functionality does not work retroactively, so information entered in this field prior to this release is not found. 

  • For new orgs, a Default Policy is no longer included in WiFi policies. 

  • We've combined the Technical Contact and End User Support Contact dialog boxes in Settings > Account. The new dialog box allows you to create a link to your help site that appears in the Home page footer. For more information, see the Account page.

    User-added image

  • Okta Mobile 5.0 features an enhanced enrollment flow that increases your end user’s visibility into which kinds of data is private and what is company accessible. For your end users to see this change in their devices, it must be enabled by Okta.

    User-added image

    For details about this Early Access (EA) feature, see Using Okta Mobile. To enable it for your end users, call Okta Support.

  • We have enhanced the Amazon Web Services (AWS) app to support the Session Duration attribute for SAML and Federated Login SSO modes. This gives Okta admins the ability to set a session duration limit, in seconds, for users. Minimum duration is 900 seconds, maximum value is 43200 seconds.

    You set the Session Duration under the app configuration's Sign On tab:

    User-added image

  • We have improved our new EA System Log by placing the three Count of events by... histogram graphs behind a Show event trends by category link, only displaying them when that link is clicked.
  • When end-users using delegated-authentication attempt to sign-in and fail after multiple attempts, our Softlock feature locks them out of Okta. If enabled, these locked-out users can then utilize Okta Self Service. Otherwise, admin action is required to unlock their Okta account.
  • We've removed the Select All option from the Assign to People step of the Add App Wizard, GA version. This helps avoid slow performance caused by assigning an app to all users in very large orgs. This change is consistent with the behavior already implemented in the EA version of the wizard.

Browser Updates

  • We have modified the phased GA rollout of the Internet Explorer (IE) browser plugin that we began on November 14, 2016 by promoting plugin version 5.9.2 as the latest GA rollout candidate. Like the previous release, this release fixes an issue that prevented the IE plugin from working with our EMEA production environment and provides performance and security enhancements. Okta strongly recommends that you install the plugin if prompted to do so. If you have any questions or concerns following the upgrade, contact Okta Support. For plugin version history, see Browser Plugin Version History.

  • We have updated the Okta plugin for the Firefox browser to version 5.9.0 for EA users. This release provides performance and security enhancements. To obtain this version, contact Okta Support.

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.

Application Updates

We've enhanced the following application integrations:

  • You can now set the canEdit licensing parameter for LucidChart.
  • We now support DocuSign's new universal login.

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

  • DocuSign (OKTA-106270)

  • IBM Workspace (OKTA-106901)

  • ISS ProxyExchange (OKTA-104202)

  • Orion Advisor (OKTA-104705)

  • SalesLoft (OKTA-107092)

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

  • Cisco Umbrella (OKTA-102534)

  • Dashlane Business (OKTA-107352)

  • Fuze Customer Portal (OKTA-104850)

  • Interact (OKTA-105570)

  • Jostle (OKTA-105921)

  • OpsGenie (OKTA-67198)

  • Pivotal Tracker (OKTA-102795)

  • RunEffective (OKTA-104860)

  • Sharpen (OKTA-102768)

  • SyncHR SAML (OKTA-107384)

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

  • TraceSecurity TraceCSO (OKTA-96112)

 

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

  • ADP Run (OKTA-107102)

  • AnyPerk (OKTA-103960)

  • Microsoft Office 365 (OKTA-106708)

  • Workplace by Facebook (OKTA-105715)

  • Microsoft Office 365 (OKTA-106708)

  • Workplace by Facebook (OKTA-105715)

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

  • Jobvite (OKTA-107637)

 

Bug Fixes

Bug numbers ending with an H are hotfixes. Hotfixes are typically deployed after the initial release.

Product Bug Fixes

The following issues are fixed:

  • OKTA-84344 – In rare cases, users were unable to set up Okta Verify with Push notification on their devices.
  • OKTA-95573 – The Admin dashboard sometimes failed with the following error: Couldn't load tasks: Refresh the page to view.
  • OKTA-59729 – When searching for apps on the end user home page, the list of apps rendered incorrectly when it contained a large number of results. 
  • OKTA-102796 – As prompting AD-mastered users to reset their passwords when they are about to expire is not supported, we have removed this setting for AD mastered users in group password policy.
  • OKTA-103145 – Non-MFA users were unable to perform SMS password resets.
  • OKTA-103512 – Group assignments to Samanage failed when None selected was chosen for the Department attribute.
  • OKTA-103587 – Enabling the JIRA On-premise app failed to function with TLSv1.2.
  • OKTA-104032 – Encrypted settings were erased after saving new SSO assignments.
  • OKTA-104570 – Moving a user from one pushed group to another failed.
  • OKTA-105268 – New end-users, authenticated through AD after activation, failed to have their last login updated in Okta reports.
  • OKTA-105394 – The RingCentral embedded log-in screen displayed incorrectly when resized in the Safari browser on OSX.
  • OKTA-106641 – Dragging a mouse over the histogram graph to narrow results in the new EA System Log failed.
  • OKTA-106787 – Adding 25 or more groups to a group filter failed under certain circumstances.
  • OKTA-107162 – Attempting to log in to Okta Mobile failed from iPhone 7 devices running iOS 10 and configured for Duo MFA.
  • OKTA-107357 – Changing an Okta user profile attribute from Inherit from Profile Master to Inherit from Okta failed.
  • OKTA-107445 – Some text was misspelled in the IWA section of Security > Authentication > Active Directory.
  • OKTA-107554 – Admins could not see the complete profile mappings template when assigned to a custom version of the CPC App.
  • OKTA-107915 – Some text was misspelled on the Nederlands language Welcome page presented to new users.
  • OKTA-108111 – In end user settings, clicking the Add Phone Number button in the Forgot Password Voice Call dialog had no effect for AD-mastered users.
  • OKTA-108185 – Creating users in Okta failed if a bookmark app was assigned to a group.

App Integrations Fixes

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

  • ADP Run (OKTA-106949)

  • Adtech US (OKTA-101404)

  • Bing Ads (OKTA-106630)

  • Cox Business (OKTA-106306)

  • Drilling Info (OKTA-107739)

  • Druva (OKTA-107248)

  • Microsoft Developer Network (OKTA-107229)

  • Moo (OKTA-107516)

  • NTEN.org (OKTA-106625)

  • Southwest Airlines (OKTA-106315)

  • Visual Studio (OKTA-106603)

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

  • Asentinel (OKTA-107493)

  • SumTotal Systems Learning
    Maestro (OKTA-104244)