Okta Production Release 2016.11 began deployment on March 21. 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.
- We have enhanced deprovisioning for Box. Admins now have new options when deprovisioning users. There is a new Box user status upon deactivation option Deleted, and also some new File management upon user deletion actions are available. For details, see Configuring Box Offboarding.
Okta is pleased to announce that our Group Membership Rules feature is now Generally Available (GA). This feature simplifies group administration. For details see Using Group Membership Rules.
Attribute-level Mastering (ALM) is now GA. ALM delivers fine-grain control over how profiles are mastered, allowing you to specify different profile masters for individual attributes. You can even allow end-users to edit specific attributes from their Settings > Account page. For more information, see Attribute Level Mastering.
We are pleased to announce we have enhanced provisioning for Microsoft Office 365. While configuring provisioning, if the admin enters the API credentials of a user who does not have the Office 365 Company Administrator role, a warning is displayed and they are prompted to enter another user.
- When users are added or removed from groups, the system log now specifies whether the change was initiated by an admin or by a rule.
On March 1, 2016, Okta discontinued support for iOS 7.x. Okta Customer Support will no longer investigate issues related to iOS 7. For more details see Okta Mobile and Okta Verify Supported Versions. To learn about Okta’s version support information, see our new Supported Configurations page.
Okta Developer Platform
Documentation for the Okta Developer Platform is available at http://developer.okta.com.
Incremental Features Summary
The following table summarizes features that are enabled incrementally. Links in the Feature column point to additional documentation for that feature, if available. After the feature is fully released, it is no longer tracked in this table. For release history of all features, see Features by Release.
|Enhanced Automatic App Login (Plugin)||2015.46||2015.46|| –|| –|
|Box for EMM||2016.09||2016.11||2016.09||2016.11|
|New User State: Suspended (GA)||2016.10||2016.11||2016.10||2016.11|
|Attribute Level Mastering (GA)||2016.11||2016.11||2016.11||2016.12 - 2016.13|
|Group Membership Rules (GA)||2016.11||2016.11||2016.11||2016.12 - 2016.13|
Browser Plugin Update
Okta announces the General Availability of browser plugin version 5.5.2 for Windows Internet Explorer (IE). This version fixes the following issues:
- Apps failed to appear in the Okta Your Apps drop-down list.
- IE11 users could not log in to SWA apps.
You can obtain this release from the Okta Downloads page (Settings > Downloads). For plugin version history, see Browser Plugin Version History.
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.
The following issues are fixed:
- OKTA-80694H – Removed a potential cross-site scripting vulnerability from group names.
- OKTA-80977 – In the Add Identity Providers page in the Authentication Settings area, some options in the Transform username selection box didn't show the formula variable idpuser.
- OKTA-81274 – Internet Explorer and Firefox failed to honor the Sign on Policy to reauthenticate after a specified time.
- OKTA-81275 – When creating a SAML 2.0 app, sign-on methods failed to appear under the Sign-On tab.
- OKTA-81876 – Some users enrolling their iOS devices in Okta Mobility Management (OMM) incorrectly received a failed installation message.
- OKTA-82795 – Group memberships were not updated in Okta following imports from Active Directory.
- OKTA-82927 – The Scopes field on the Edit Identity Provider page failed to save scopes that were entered manually.
- OKTA-83365 – The 30-day activity widget on the Device page failed to include devices with a Checkout status.
- OKTA-84385H – Users whose IWA account setup was incomplete were unexpectedly prompted to complete the new-user setup.
The following SWA apps were not working correctly and are now fixed: