Production release notes

Help us improve our release notes by filling out this short survey.

Current release status

Current Upcoming
Production 2023.09.0 2023.09.1 Production release is scheduled to begin deployment on September 25
Preview 2023.09.1

2023.09.2 Preview release is scheduled to begin deployment on September 27

September 2023

2023.09.0: Monthly Production release began deployment on September 18

* Features may not be available in all Okta Product SKUs.

Content

Generally Available Features

Sign-In Widget, version 7.10.0

For details about this release, see the Sign-In Widget Release Notes.

For more information about the Widget, see the Okta Sign-In Widget Guide.

Okta LDAP agent, version 5.18.0

This version of the agent contains security enhancements.

Note: In Windows, the LDAP Agent auto-update feature isn't capable of deploying all security enhancements that are introduced in version 5.18. To completely deploy all security enhancements from this release, all LDAP agents running version 5.17 or earlier must be uninstalled, and version 5.18 must be manually installed. See Install the Okta LDAP Agent.

Okta MFA Credential Provider for Windows, version 1.3.9

This release includes bug fixes, security enhancements, and support for an additional top-level domain. See Okta MFA Credential Provider for Windows Version History.

Chrome Device Trust connector integration

With the introduction of the Chrome Device Trust Connector integration for Device Assurance, administrators can create policies that ensure compliance with specific device requirements prior to accessing resources protected by Okta. This integration between Okta and Google facilitates access policies that receive device posture signals directly from a Google API backend, eliminating the need for any agent deployment. As a result, users logging in to a ChromeOS device, or managed Chrome browser, benefit from enhanced authentication security through device security signals.

Authentication challenge for redirects

Users now receive an authentication challenge for each redirect sent to an Identity Provider with Factor only configured, even if the IdP session is active.

Access Testing tool

With the Access Testing tool you can quickly and easily test policies and validate whether your desired security outcomes will be achieved. This tool allows you to simulate user access attributes, such as IP address, device, risk, and so on, to test whether the user will be granted access to the specified application. The tool helps you identify potential security risks and compliance issues before you implement a policy. See Access Testing Tool.

Custom Identity Source app available

The Custom Identity Source app is now available in Okta Integration Network.

Count summary added to report

The User accounts report now displays the total number of records returned for the report.

Product Offers dashboard widget

A Product Offers widget now displays on the Admin Dashboard for super and org admins. The widget provides a cost- and commitment-free way for admins to explore and test the capabilities of various Okta products. When a new free trial is available, admins can click Get started to activate it, or Not interested to dismiss the widget.

Okta Verify requirements for self-service upgrades

Orgs with incorrect Okta Verify enrollment settings are now notified of configuration requirements before they upgrade to Identity Engine.

Automatically assign the super admin role to an app

Admins can now automatically assign the super admin role to all of their newly created public client apps. See Work with the admin component.

Device attributes label update

Some device attribute labels are renamed for clarity and to accommodate the new Chrome Device Trust connector.

Okta apps and plugin no longer available to certain users

Beta users of the PingFederate MFA plugin can no longer create Okta apps or download the plugin.

Early Access Features

Custom admin roles with device permissions

You can now create custom admin roles with permissions to view and manage devices. You can add the Devices to your resource set and then specify device permissions for your custom admin. See Create a resource set and Devices permissions.

Okta FastPass and Smart Card options on Sign-in page

Currently, if you configured both the Sign in with Okta FastPass option and Smart Card as an authenticator, users only see the Okta FastPass option when they sign in. With this feature, you can make both options available for your users during the sign-in process. See Configure the Smart Card authenticator.

Enhanced security of Okta Verify enrollments

To ensure users enroll in Okta Verify in a phishing-resistant manner, a Higher security methods option now appears on the authenticator configuration page. With this option, users can't enroll with QR code, email, or SMS link. See Configure Okta Verify options.

Fixes

  • OKTA-570804

    The RADIUS Server Agent installer for versions 1.3.7 and 1.3.8 didn't prompt users to install missing C++ runtime libraries on Microsoft Windows servers.

  • OKTA-574216

    Reconciling group memberships sometimes failed for large groups.

  • OKTA-578184

    The inbound delegated authentication endpoint didn't correctly handle errors when the authentication request wasn't associated with an org.

  • OKTA-592745

    Full and incremental imports of Workday users took longer than expected.

  • OKTA-605996

    A token inline hook secured by an OAuth 2.0 private key returned an error for all users except super admins.

  • OKTA-616604

    The password requirements list on the Sign-In Widget contained a grammatical error.

  • OKTA-616905

    Events weren't automatically triggered for Add assigned application to group, Remove assigned group from application, and Update Assign application group event hooks.

  • OKTA-618302

    Application users weren't created when a required application user attribute was missing.

  • OKTA-619102

    Invalid text sometimes appeared in attribute names.

  • OKTA-619179

    A timeout error occurred when accessing a custom report for UKG Pro (formerly UltiPro).

  • OKTA-619419

    Group admins could see their org’s app sign-in data.

  • OKTA-624387

    Sometimes attempting to change an app's username failed due to a timeout.

  • OKTA-627559

    Access policy evaluation for custom authorization servers was inconsistent when default scopes were used.

  • OKTA-628944

    Email notifications from Okta Verify were sent from the default domain address instead of the email address configured for the brand.

  • OKTA-631621

    Read-only admins couldn't review the details of IdP configurations.

  • OKTA-633431

    When an Okta Org2Org integration encountered an API failure, the resulting error message was displayed in Japanese.

  • OKTA-634308

    Group app assignment ordering for Office 365 apps couldn't be changed.

  • OKTA-636839

    Smart Card IdP users couldn't set a password after signing in for the first time.

  • OKTA-637259

    An error occurred when importing users from Solarwinds Service Desk.

  • OKTA-641062

    The link to Slack configuration documentation was invalid.

  • OKTA-641447

    Super admins couldn’t save new custom admin roles.

  • OKTA-648092

    New admins didn't get the Support app in their End-User Dashboard.

Okta Integration Network

App updates

  • The CoRise app integration has been rebranded as Cobalt.

New Okta Verified app integrations

App integration fixes

  • American Express Online (OKTA-637925)
  • hoovers_level3 (OKTA-637274)
  • MSCI ESG Manager (OKTA-637624)
  • PartnerXchange (OKTA-632251)
  • Staples Advantage (OKTA-639141)

August 2023

2023.08.0: Monthly Production release began deployment on August 14

* Features may not be available in all Okta Product SKUs.

Content

Generally Available Features

Okta AD agent, version 3.16.0

When the executor.log and coordinator.log files exceed 5 MB in size, the contents roll over into executor.log.old and coordinator.log.old files.

Okta Active Directory Federation Services Plugin, version 1.7.13

Version 1.7.13 of the Okta Active Directory Federation Services (ADFS) Plugin is now available for download. It includes support for Microsoft Windows Server 2022 and includes bug fixes and security hardening. See Okta ADFS Plugin version history.

Telephony inline hook required for phone authenticator

New orgs now require a Telephony inline hook to use the phone authenticator. You can connect an external telephony provider with Okta using the inline hook. See Phone authenticator. Alternatively, you can acquire the Okta SMS/Voice SKU.

Redesigned resource set pages

The Create new resource set and Edit resource set pages that are displayed when an admin creates or edit a resource set now provide a simpler, more intuitive user experience. See Create a resource set.

Hardware-protected FIDO2 WebAuthn available

Hardware-protected FIDO2 WebAuthn as defined by the FIDO Metadata Service is now available in authentication policies when the Hardware-protected checkbox is selected. See About MFA authenticators.

Integrate with any identity source

To get Okta's full HR-driven provisioning and LCM functionality for an HR integration, customers previously had to use one of five pre-integrated HR systems or build complex custom code with the Okta Users API to replicate some of Okta’s LCM functionality for other identity sources.

With Anything-as-a-Source (XaaS), customers now have the flexibility to connect any identity source to Okta and realize the full benefits of HR-driven provisioning with a simpler solution. See Anything-as-a-Source.

Smart Card authenticator available

You can add a new Smart Card authenticator that enables PIV to be used in authentication policies. You can also restrict the authentication policies to use only Smart Card Authenticator as MFA. See Configure the Smart Card authenticator.

Getting Started video for new orgs

The Getting Started page now displays an introductory video. The video provides a quick overview of the common tasks and functions for new orgs, and helps admins familiarize themselves with the Admin Console. See Get started with Okta.

API service integration client secret rotation in the Admin Console

New in this release is the ability to rotate client secrets for an API service integration through the Admin Console. Previously, if a customer wanted to update the client secret for an API service integration, they had to reinstall the integration to obtain a new client ID and secret. There was no option to revoke the client secret while maintaining the client ID and API service integration instance in Okta. With this new feature, customers can generate a new secret, deactivate an old secret, and remove a deactivated secret from the API service integration instance. These functionalities help customers implement security best practices without service downtime. See API Service Integrations.

New event types for User Auth Events

Two additional event types are now available under User Auth Events:

  • User's session was cleared
  • User's MFA factor was updated

New application lifecycle event hook

An event hook to deny user access due to a condition in an authentication policy is now available to admins. See Create an event hook .

Polling enhancements for Agentless DSSO

When the server is in SAFE_MODE, Agentless DSSO polling signs in a user if they are in ACTIVE state in Okta.

Early Access Features

Early Access features from this release are now Generally Available.

Fixes

  • OKTA-575884

    The Okta Active Directory Federation Services (ADFS) Plugin wrote errors to the plugin log when users attempted to sign in.

  • OKTA-595086

    The display of the authorization server Access Policies page froze with large numbers of policies.

  • OKTA-596293

    After upgrades to Identity Engine, users were sometimes asked to re-authenticate when refreshing their Okta dashboards even though the sessions were still valid.

  • OKTA-606898

    Some users got stuck in a password expiration warning loop when they signed in with AD delegated authentication and updated their password.

  • OKTA-610347

    Some orgs couldn't add more than 50 global session policies.

  • OKTA-617816

    After orgs upgraded to Identity Engine, the application name in OV Push disappeared.

  • OKTA-626699

    On the Administrator assignment by admin page, the Role dropdown list sometimes displayed duplicate admin roles.

  • OKTA-626968

    The error message that appeared when the admin attempted to add an inactive Smart Card IdP to the authenticator didn't mention the name of the IdP.

  • OKTA-631657

    Users were sometimes improperly redirected to a device-posture provider when none was configured in the authentication policy.

  • OKTA-631752

    Adding some IdPs as Factor only caused errors.

  • OKTA-632786

    Admins could require Smart Card in an authentication policy even when it wasn't set up as an authenticator.

Applications

New Integrations

New SCIM Integration applications

The following partner-built provisioning integration apps are now Generally Available in the OIN:

SAML for the following Okta Verified applications

OIDC for the following Okta Verified applications

Weekly Updates

Fixes

  • OKTA-619028

    Read-only admins received user reports of suspicious activity email notifications in error.

  • OKTA-624193

    The Access Testing Tool results showed an incorrect value for the profile enrollment self-service registration option.

  • OKTA-627533

    Removing the emailAuthenticationLink variable from the email template didn't update the Sign-In Widget.

  • OKTA-631142

    Orgs using a custom client_id in their OAuth2 client apps were unable to delete enrolled users.

  • OKTA-632131

    OpenID Connect /token requests using the SAML 2.0 Assertion grant type flow failed if the SAML assertion expiry was greater than 30 days.

  • OKTA-632850

    Slack provisioning didn't automatically retry after exceeding rate limits.

  • OKTA-633585

    The on-demand auto-update banners for the Active Directory agent displayed updates in a random order.

  • OKTA-634923

    Users weren't present in the import queue after being unassigned from an app.

  • OKTA-635579

    When a super admin went to the Groups Admin Roles tab, the Edit group assignments button was mislabeled.

  • OKTA-636652

    The Administrators page wasn’t translated to Japanese.

Applications

Application Update

  • Group push and group import is now available for the Smartsheet SCIM integration.

New Integrations

New SCIM Integration applications

The following partner-built provisioning integration apps are now Generally Available in the OIN Catalog as partner-built:

SAML for the following Okta Verified applications:

OIDC for the following Okta Verified applications:

Fixes

  • OKTA-601623

    When configuring an API Service Integration (either through the Admin Console or using APIs), admins could set a JWKS URL using HTTP instead of HTTPS.

  • OKTA-620953

    When user enumeration prevention wasn't enabled, the UserId and user profile were visible in the network response prior to authentication.

  • OKTA-621214

    Long custom label text was sometimes truncated on the Sign-In Widget during enrollment.

  • OKTA-621253

    Email Change Confirmed Notification messages weren't sent if the audience was set to Admin only.

  • OKTA-627175

    Some tasks displayed a greater-than sign (>) instead of the date.

  • OKTA-630368

    RADIUS logs showed multiple, repetitious Invalid cookie header warning messages.

  • OKTA-634010

    Users who were locked out of Okta but not Active Directory could receive Okta Verify push prompts and sign in to Okta.

  • OKTA-637641

    Some users received a Bad Request error when they signed in with Okta FastPass.

  • OKTA-639427

    When admins added a new user in Preview orgs, the Realm attribute appeared on the dialog.

Applications

New API Service Integration applications:

OIDC for the following Okta Verified applications:

Fixes

  • OKTA-620655

    When an error occurred during Identity Engine upgrades, a Customer Config Required message appeared instead of an Okta Assistance Required message.

  • OKTA-622753

    The Access Testing Tool allowed access to applications even though authenticator enrollment was denied.

  • OKTA-641043

    Admins could select values from disabled dropdown menus.

Applications

Okta Verified applications:

July 2023

2023.07.0: Monthly Production release began deployment on July 17

* Features may not be available in all Okta Product SKUs.

Content

Generally Available Features

Sign-In Widget, version 7.8.0

For details about this release, see the Sign-In Widget Release Notes.

For more information about the Widget, see the Okta Sign-In Widget Guide.

Okta LDAP agent, version 5.17.0

This version of the agent contains:

  • Migration of the Windows installer from Internet Explorer to Edge
  • The service OktaLDAPAgent stop command now correctly terminates agents installed on Red Hat and CentOS platforms
  • Security enhancements

See Okta LDAP Agent version history.

System Log time zone formats updated

In the System Log, the time zone dropdown menu now provides additional information about each available time zone. See System Log.

App Password Health report uses browser time zone

On the App Password Health report, last-reset request dates and times are now based on the browser’s time zone settings. See App Password Health report.

Okta-generated client secret length increase

The length of Okta-generated client secrets is increased from 40 to 64 characters.

Updated Okta logo

A branding update to the Okta groups logo is now available in the Admin Console.

RADIUS sign-in error prevention

For orgs that upgraded from Classic Engine, if the Okta Verify authenticator is configured with number challenge, the challenge may be presented unexpectedly to RADIUS users. This can prevent users from using RADIUS with Okta Verify because RADIUS doesn't support the number challenge today. For upgraded orgs, a new feature is enabled that prevents any such errors. See RADIUS applications in Okta.

New authenticator management functionality

Okta now enables you to manage which authenticators are allowed in your org for new enrollments, authentication enrollment policies, and user verification. You can view a list of all Okta-recognized authenticators, create authenticator groups, and use them in policies. This allows admins to have greater control over which authenticators may be used in their orgs and determine which users may access them in a granular way. See Configure the FIDO2 (WebAuthn) authenticator.

Google Authenticator available for account recovery

Admins may now allow their users to initiate account recovery scenarios with Google Authenticator, Email, Phone, or Okta Verify. Increasing the number of options available for recovery enhances the user experience. See Configure the Password authenticator.

Early Access Features

IdP permissions for custom admin roles

Admins can now leverage new Identity Provider management permissions when creating custom admin roles. These permissions allow more precise access control and reinforce the principle of least privilege. See About role permissions.

Redesigned admin role pages

The Create a role and Edit role pages for custom admin-role configuration now provide a simpler, more intuitive user experience. See Create a role.

Admin Console Japanese translation

When you set your display language to Japanese, the Admin Console is now translated. See Supported display languages.

IME support for international characters

Admins can now use an Input Method Editor (IME) to type international characters into the Admin Console.

Front-channel Single Logout

Front-channel Single Logout (SLO) allows a user to sign out of an SLO-participating app on their device and end their Okta session. Okta then automatically sends a sign-out request to all other participating apps that the user accessed during their session. See Configure Single Logout in app integrations.

Fixes

  • OKTA-556787

    During step-up verification, multiple indistinguishable enrollments for the smart card authenticator were displayed. Now only one smart card authenticator enrollment is displayed.

  • OKTA-602939

    The Admin role assignments report email wasn’t translated.

  • OKTA-615453

    Some text strings were incorrect on the End-User Dashboard layout page.

  • OKTA-623542

    The link to the Access Policy Simulation help topic on the Features page was incorrect.

Applications

Application Updates

  • The Rybbon app integration has been rebranded as BHN Rewards.

New Integrations

New SCIM Integration applications

The following partner-built provisioning integration apps are now Generally Available in the OIN:

  • Apono: For configuration information, see Okta SCIM.

SAML for the following Okta Verified applications

App Integration Fixes

The following SWA app was not working correctly and is now fixed:

  • BlueHost (OKTA-620224)

Weekly Updates

Fixes

  • OKTA-457661

    Testing the Agentless Desktop Single Sign-on configuration with an active Okta session failed with an error.

  • OKTA-599540

    HTTP replies to SP-initated SAML requests contained two session IDs, which sometimes caused user sessions to expire unexpectedly.

  • OKTA-605041

    An unclear error message appeared when an admin created a role or resource set with a long name.

  • OKTA-606195

    Some users couldn't access Okta on a shared workstation until they cleared cookies from the browser.

  • OKTA-606938

    Log streaming apps were incorrectly included in the number of assigned apps shown for the default policy on the Authentication policies page.

  • OKTA-612727

    The Admin Dashboard Tasks table displayed an incorrect amount of provisioning capable apps.

  • OKTA-612875

    After managerId was removed from the Salesforce schema in Okta, it couldn't be added again.

  • OKTA-613076

    In the Sign On tab of Office 365, the Okta MFA from Azure AD option appeared disabled. When the option was switched to edit mode, it was enabled.

  • OKTA-613162

    Admin couldn't manually create a new user with a password when password was configured as an optional authenticator.

  • OKTA-613394

    Users couldn't sign in with a PIV in an Org2Org flow.

  • OKTA-615345

    Some admins couldn't view the password for SWA applications that were assigned a common username and password.

  • OKTA-615407

    For custom SAML apps, the last-selected authenticator wasn't saved and reused for subsequent admin sign-in events.

  • OKTA-615441

    Some users couldn't sign in with Agentless Desktop Single Sign-on because routing rules were re-evaluated during the sign-on process.

  • OKTA-615457

    The Edit resources to a standard role page didn’t display apps that had the same name.

  • OKTA-617528

    The auto-update schedules for the Active Directory and LDAP agents were incorrectly shown as up-to-date, even when a new version was released.

  • OKTA-617817

    Admins were sometimes unable to access the Admin Console from a custom domain.

  • OKTA-618825

    The Okta-hosted Sign-In Widget displayed the wrong error message to users who were locked out.

  • OKTA-619704

    Newly provisioned users who signed in with a PIV prior to setting a password couldn't set a password later without admin intervention.

  • OKTA-620153

    ACS URL validation failed for orgs that used SAML SSO with Okta-to-Okta IdP configurations and had subdomain names that weren't all lowercase characters.

  • OKTA-620651

    Validation messages that appeared during a self-service upgrade to Identity Engine incorrectly stated that a configuration change was required.

  • OKTA-622541

    In the Self-Service Unlock when Account is not Locked email template, the base URL variable wasn’t replaced with the Okta tenant URL.

  • OKTA-626022

    Some Active Directory agents that had previously failed to auto-update were incorrectly marked as Queued for update, despite being updated to the latest version.

  • OKTA-627415

    On the Features page, the link to access the LDAP Agent Auto-update documentation was broken.

  • OKTA-628522

    RADIUS agent libraries contained internal security issues. Fixes require upgrading to agent version 2.19.0 and using Microsoft Edge as the browser.

Applications

Application Update

  • The OpenPath app integration has been rebranded as Avigilon Alta.

New Integrations

New SCIM Integration applications

The following partner-built provisioning integration apps are now Generally Available in the OIN Catalog:

SAML for the following Okta Verified applications

OIDC for the following Okta Verified applications

Generally Available

Sign-In Widget, version 7.8.2

For details about this release, see the Sign-In Widget Release Notes.

For more information about the Widget, see the Sign-In Widget Guide.

Fixes

  • OKTA-604448

    Some text on the Groups page wasn't translated.

  • OKTA-613162

    Admin couldn't manually create a user with password when password was configured as an optional authenticator.

  • OKTA-618825

    The Okta-hosted Sign-In Widget displayed the wrong error message to users who were locked out.

  • OKTA-620583

    On the Add Resource dialog, the list of search results was misaligned.

  • OKTA-620873

    Admins couldn't upload PEM-formatted certificates containing encrypted private keys for RADIUS apps.

  • OKTA-622783

    The initial expiresIn date for the Salesforce authentication token wasn't set from the API.

  • OKTA-626593

    Admins couldn’t access the Create new resource set page directly from a URL.

  • OKTA-631303

    Admins couldn't access the Administrator assignment by role page. This occurred when a public client app with a custom client ID was assigned a standard admin role.

Applications

New Integrations

SAML for the following Okta Verified applications:

OIDC for the following Okta Verified applications:

App Integration Fixes

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

  • E-OSCAR (OKTA-624390)

  • UPS (OKTA-625886)

  • UPS CampusShip (OKTA-624286)