Okta Identity Engine release notes (Production)

July
June
May

Version: 2025.07.0

July 2025

Generally Available

Sign-In Widget, version 7.33.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.

Release notes available in Japanese

Release notes for Okta Identity Engine are now translated to Japanese for each release. These translations are published within a week of the English publication.

Okta Provisioning agent, version 2.3.1

This release contains security enhancements. See Okta Provisioning Agent and SDK version history.

Enhanced security for End User Settings

End User Settings version 2.0 now performs policy evaluations before granting new access tokens.

Okta Hyperdrive agent, version 1.5.1

This version includes security enhancements.

Automatic certificate enrollment for certificate-based authentication in WS-Fed SSO

Automatic certificate enrollment is now supported for certificate-based authentication in WS-Fed SSO requests. Users can authenticate with smart/PIV cards without setting up smartcards, allowing seamless access to their Windows devices and Office 365 apps.

Claims sharing enhancement

Claims sharing between Identity Engine orgs now supports the inclusion of authentication policy and global session policy rules that include authentication method chains. This enhancement gives admins greater flexibility when designing authentication for org-to-org scenarios. See Add a SAML Identity Provider.

Okta LDAP agent, version 5.24.0

This version of the agent includes the following:

Configuration files are now encrypted
Local LDAP agent configuration files are monitored for unexpected changes
install.log created to help debug installation issues
Security enhancements

Enhancement for advanced posture checks

Admins can now configure advanced posture checks to appear as a checkbox or textbox in device assurance policies.

Google Workspace improvements

The following changes have been made to improve the performance of the Google Workspace app integration:

More robust group-related error handling
Eliminated duplicate group creation upon import when Import Groups is disabled

Okta MFA Credential Provider for Windows

This release includes bug fixes and security enhancements.

New label for admin-initiated security methods

The My Settings > Security methods page now displays an Enrolled by admin label on admin-initiated security methods.

Name matching for identity verification

Admins can now map attributes for both preferred and legal first and last names when sending verification claims to an identity verification (IDV) vendor. This improves the accuracy of verification and gives the admin control over which attributes are sent to the vendor.

Conditions for create user permission

You can now add conditions to the Create user permission for custom admin roles. This enables you to granularly control which user attributes admins can set values for during user creation. See Permission conditions.

Bypass ASN binding with the Default Exempt IP Zone

The ASN binding feature associates admins with the IP address that they signed in from. If the IP changes during a session, the admin is signed out of Okta, and an event appears in the System Log. To bypass IP and ASN binding, you can add the client IP to the Default Exempt IP Zone. See IP exempt zone.

New identity verification provider added

Okta now supports using Incode and CLEAR Verified as identity providers. This increases the number of identity verification vendors (IDVs) you can use to verify the identity of your users when they onboard or reset their account. See Add an identity verification vendor as an identity provider.

New validation rule for user profile attributes in OIN Wizard

The OIN Wizard now requires the use of valid user profile properties when referencing attribute values in EL expressions. The system rejects any invalid user EL expressions and attributes that aren't included in the allowlist. See Define attribute statements.

Secure Partner Access for external partners

Secure Partner Access provides a secure way for external business partners to access your org's resources. It streamlines your partner management tasks, reduces IT workload, and simplifies the process of configuring your org's security requirements. See Manage Secure Partner Access.

Certificate-based authentication for Office 365

Okta Identity Engine now supports certificate-based authentication for WS-Fed SSO requests. Users can authenticate using smart/PIV cards to seamlessly access their Windows devices and Office 365 apps.

Manage Subscription button removed

The Manage Subscription button has been removed from the Settings page.

New look and feel in the Admin Console

The Admin Console now provides a new look and feel, including redesigned side and top navigation menus and the addition of a gray background.

New look and feel in the End-User Dashboard

The End-User Dashboard now provides a new look and feel, including redesigned side and top navigation menus and the addition of a gray background.

Restrict access to the Admin Console

By default, users and groups with assigned admin roles have access to the Admin Console app. With this feature, super admins can choose to manually assign the app to delegated admins instead. This is recommended for orgs with admins who don't need access, like business partners, third-party admins, or admins who only use the Okta API. See Configure administrator settings.

Early Access

Network restrictions for OIDC token endpoints is EA in Preview

You can now apply network restrictions to OIDC token endpoints to enhance token security. See Create OpenID Connect app integrations.

Okta Integration IdP type is EA in Preview

The Okta Integration IdP allows you to use an Okta org as an external IdP, simplifying configuration and providing secure defaults. See Add an Okta Integration Identity Provider.

Universal Directory map toggle

The new Universal Directory (UD) map toggle enables admins to link a user's email address to their identifier. This allows admins to enable the self-service registration feature. See General Security.

OAMP protection for password expiry flows

This feature improves the security posture of customer orgs by protecting the password expiry flow with the Okta account management policy. Password expiry flows now require the assurance defined in an org's Okta account management policy. See Enable password expiry.

Enforce MFA for Identity Governance admin apps

The Enforce MFA for Identity Governance admin apps feature is no longer available as a self-service Early Access feature. Admins must contact Okta Support to enable or disable this feature. See Enable MFA for the Admin Console.

OU moves for LDAP-provisioned users

When an admin configures Okta to LDAP provisioning settings, they can now move users to a different Organizational Unit (OU) by changing their group assignments. See Configure Okta to LDAP provisioning settings.

Okta Hyperspace agent, version 1.5.1

This version includes security enhancements.

System Log event for monitoring LDAP Agent config file changes

A system.agent.ldap.config_change_detected event is generated when an LDAP agent detects changes to its configuration file.

On-prem Connector for Oracle EBS

On-prem Connector for Oracle EBS connects Oracle EBS on-premises apps with Okta Identity Governance. It helps admins discover, view, and manage Oracle EBS entitlements directly in Okta. This integration enhances security, saves time, streamlines entitlement management, and eliminates the need for custom integrations. See On-prem Connector for Oracle EBS and Supported entitlements by On-prem Connector.

Integrate Okta with Device Posture Provider

The Device Posture Provider feature enhances Zero Trust security by integrating external device compliance signals into the Okta policy engine. Previously, Okta couldn't leverage signals from third-party or custom tools to enforce access policies. Now, by accepting SAML/OIDC assertions from external compliance services, admins can incorporate custom compliance attributes into device assurance policies. This enables organizations to utilize their existing device trust signals within Okta, and foster a more flexible and secure posture without the need for extra agents or redundant tooling. See Integrate Okta with Device Posture Provider.

Provisioning for Oracle Human Capital Management

Provisioning is now available for the Oracle Human Capital Management app integration. When you provision the app, you can enable security features like Entitlement Management, Privileged Access, and more. See Oracle Human Capital Management.

Fixes

The Grace period for device assurance feature didn't apply to Chrome Device Trust users. (OKTA-817660)
Group push errors were displayed for app instances that didn't have provisioning enabled. (OKTA-924631)
Client location, IP address, and user agent weren't visible for security.breached_credential.detected events in System Log. (OKTA-934324)
In orgs with user enumeration prevention enabled, users who locked out their account saw an incorrect warning in the Sign-In Widget. (OKTA-939242)
When any of the When a user is reactivated in the app options were enabled for an app integration, the first attempt to re-login using ADSSO by disconnected AD users failed. (OKTA-939542)
Additional roles couldn't be added to the base Role attribute for SmartRecruiters app integrations. (OKTA-944146)
Users on devices with small viewports were unable to sign out. (OKTA-958188)
Editing a previously blank default value of an attribute in the Profile Editor failed if the Attribute length was set. (OKTA-958747)
Some users who were logged out of Okta by the breached credentials protection feature had custom attribute values deleted from their user profile. (OKTA-964312)

Okta Integration Network

Cockroach Labs (SCIM) is now available. Learn more.
Grace (OIDC) is now available. Learn more.
Hive (SCIM) is now available. Learn more.
Optmyzr (OIDC) is now available. Learn more.
Planfix (SCIM) is now available. Learn more.
Planfix (SAML) is now available. Learn more.
Splunk Add-on for Okta Identity Cloud (API integration) is now available. Learn more.

Weekly Updates

2025.7.1: Update 1 started deployment on July 14

Generally Available

Sign-In Widget, version 7.33.1

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

Fixes

Some users had to authenticate with their passwords twice when signing in to Okta to access a bookmark app in orgs where Okta Verify Push was required as the second authenticator. (OKTA-817382)
In some OIE preview orgs with routing rules, users who clicked the embedded URL of an app were incorrectly sent to the IdP, even though they weren't assigned to that app. (OKTA-827133)
Users were deactivated during imports where Super Admin privileges had been granted through group membership assignment. (OKTA-831811)
Some users with custom admin roles were unable to use the authorization server token preview. (OKTA-847900)
Users weren't able to validate MFA through FIDO2, Okta Verify Push, or TOTP authentication if the OrgUrl contained a trailing slash character or uppercase letters. (OKTA-897324)
The multiple identifiers feature didn't process case sensitivity correctly when evaluating identifier attributes. (OKTA-899235)
Users were unable to enroll in Okta Verify on their mobile device when signing in to an org using the Okta Org2Org app. (OKTA-926590)
Some users saw an error when they tried to load the list of apps mapped to a policy. (OKTA-934678)
The create user form didn't clearly indicate whether an admin can view or edit the files, which caused confusion during user creation. (OKTA-953319)
When the /login/agentlessDsso test login flow was used with a null state token, a null pointer exception occurred. (OKTA-958088)
The Networks page became unresponsive when admins clicked the Show more option. (OKTA-958764)
Users were unable to create a new schema property using a previously used name due to an incomplete cleanup process of deleted schema properties. (OKTA-963030)
A blank page was displayed after an Okta user was successfully converted to a service account. (OKTA-969178)
The create user form didn't clearly indicate whether an admin can view or edit the files, which caused confusion during user creation. (OKTA-971861)

Okta Integration Network

NVIDIA Identity Federation (SCIM & SAML) is now available. Learn more.
Zoho Directory (API Integration) is now available. Learn more.

2025.7.2: Update 2 started deployment on July 21

Generally Available

Sign-In Widget 7.33.2

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

Fixes

Authentication policies timed out if they included a lot of app instances. (OKTA-886236)
The System Log displayed an inaccurate risk level for Entity Risk Policy Action Cleared User Risk detections. (OKTA-944114)
Some users saw an error when they tried to access the End User Settings version 2.0. (OKTA-944786)
When the Direct Authentication feature was enabled, admins with a custom role couldn't create OIDC apps. (OKTA-970705)
The options to add WebAuthn and set permission conditions weren't available on the Partner Admin Portal. (OKTA-971778)
The create user form didn't clearly indicate whether an admin can view or edit the files, which caused confusion during user creation. (OKTA-971861)
Provisioning new users without a password to on-premises SAP instances failed, even when Sync Password was disabled. (OKTA-973324)
The create user form didn't clearly indicate whether an admin can view or edit files, which caused confusion during user creation. (OKTA-977736)
This release includes security enhancements. (OKTA-984152)

Okta Integration Network

CaterCow (OIDC) is now available. Learn more.
Cato Portal has a new Redirect URI. Learn more.
DevRev (SAML) is now available. Learn more.
DevRev (SCIM) is now available. Learn more.
Fastly has a new configuration guide. Learn more.
Fastly (SCIM) is now available. Learn more.
Hexnode (API service) is now available. Learn more.
ImmuniWeb (OIDC) is now available. Learn more.
Observe.ai (Provisioning)(SCIM) is now available. Learn more.
SmartCompany is now OneHR.
Sociabble (OIDC) is now available. Learn more.
Sociabble (SAML) is now available. Learn more.

2025.7.3: Update 3 started deployment on August 4

Generally Available

Device assurance OS version updates

The following OS versions are now supported in device assurance policies: - Windows 10 (10.0.17763.7558, 10.0.19044.6093, 10.0.19045.6093) - Windows 11 (10.0.22621.5624, 10.0.22631.5624, 10.0.26100.4652)

Sign-In Widget, version 7.33.3

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

Fixes

When signing in to Okta, AD-sourced users were prompted that their password would expire, even with a password policy set to never expire. (OKTA-931026)
Read-only admins couldn't view event hooks. (OKTA-935143)
Admins couldn't identify when user enumeration settings were changed or who changed them. (OKTA-945576)
When users tried to sign in to the End-User Dashboard and an error occurred, the custom error page wasn't displayed. (OKTA-963685)
When an admin with a custom role was deactivated and then immediately reactivated, they temporarily retained their former privileges and could access the Admin Console. (OKTA-968997)
Users with case-insensitive usernames didn't match to existing strict case-sensitive users. (OKTA-969228)
Provisioning new users without a password to on-premises SAP instances failed, even when Sync Password was disabled. (OKTA-973324)
Admins couldn't create a user under a passwordless enrollment policy without setting a password. (OKTA-976891)
The create user form didn't clearly indicate whether an admin can view or edit files, which caused confusion during user creation. (OKTA-977736)
When users clicked outside of the Sign-in Widget (third generation), error messages disappeared even though the errors weren't resolved. (OKTA-888819)
The Stay signed in option for the post-authentication Keep me signed in feature didn't work in orgs with embedded Sign-In Widgets. (OKTA-921958)
Customers couldn't upgrade to Identity Engine when their Classic Engine org used a custom domain, didn't have custom sign-in page, and used version 5.10 or earlier of the Sign-In Widget. (OKTA-961939)
Users appeared twice in the results of the User App Access report. (OKTA-963812)
Some users encountered an error during self-service registration if they entered a value that already existed in the directory. (OKTA-965382)
When an admin managed Active Directory users and groups in Okta, the events didn't always appear in the System Log. (OKTA-976990)
Some Active Directory users saw a password expiration notice after the breached credentials protection feature had already expired their passwords. (OKTA-979447)
When admins cleared a user's sessions and selected Also include logout enabled apps and Okta API tokens, factors remembered by Keep me signed in for that user weren't cleared. (OKTA-979580)
The default value of a custom property reset whenever it was edited. (OKTA-983015)
Some users saw an error when they tried to assign groups in the JIT Settings of their social login identity provider. (OKTA-983565)
After signing in to an Office 365 app and redirecting back to Okta, some AD-sourced users remained in a DEACTIVATING state. (OKTA-986550)

Version: 2025.06.0

June 2025

Generally Available

Sign-In Widget, version 7.32.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.

Device assurance OS version updates

The following OS versions are now supported in device assurance policies:

Android 13, 14, 15 security patch 2025-06-01
iOS 15.8.4
iOS 16.7.11
iOS 18.5
macOS Ventura 13.7.6
macOS Sonoma 14.7.6
macOS Sequoia 15.5
Windows 10 (10.0.17763.7314, 10.0.19044.5854, 10.0.19045.5854)
Windows 11 (10.0.22621.5335, 10.0.22631.5335, 10.0.26100.4061)

Personal apps excluded from apps count

On the Admin Dashboard, the Total apps count on the Apps widget now excludes personal apps. This provides a more accurate apps count for the org. See Monitor your apps.

Per-app SAML certificate expiry notifications

The Tasks page now displays certificate expiry notifications for individual SAML apps.

New help message for custom domains

Admins creating an Okta-managed custom domain now see a message encouraging them to add a CAA record.

App permissions no longer include agent permissions

Now when you assign the Manage applications permission to an admin, the Manage agents permission isn't automatically granted. For existing admin role assignments that include the Manage applications permission, the Manage agents permission is retained in the assignment. See Role permissions.

Okta Provisioning Agent now supports Group Push with SCIM 2.0

You can now use Group Push with on-premises apps by using Okta Provisioning Agent and SCIM 2.0. See Create SCIM connectors for on-premises provisioning.

New look and feel in the Partner Admin Portal app

The Partner Admin Portal app pages now have a new look and feel, including redesigned side and top navigation menus.

Define default values for custom user attributes

You can now define default values for custom attributes in a user profile. See Add custom attributes to an Okta user profile.

Domain restrictions on Realms

You can now limit users to a specific domain in Realms, which adds an extra layer of oversight for realm and partner admins and enforces boundaries between user populations. See Manage realms.

Authentication claims sharing between Okta orgs

Authentication claims sharing allows an admin to configure their Okta org to trust claims from third-party IdPs during SSO. Sharing claims also allows Okta to interpret the authentication context from an IdP. This helps eliminate duplicate factor challenges during user authentication and helps improve security posture. See Add a SAML Identity Provider.

Improvements to Okta RADIUS

Okta RADIUS now supports Java version 17 and has a new 64-bit installer.

Authentication claims sharing between Okta orgs

Authentication claims sharing allows an admin to configure their Okta org to trust claims from IdPs during SSO. Sharing claims also allows Okta to interpret the authentication context from an IdP. This helps eliminate duplicate factor challenges during user authentication and helps improve security posture. See Add a SAML Identity Provider.

Create dynamic resource sets with conditions

Resource set conditions help you limit the scope of a role by excluding an admin's access to certain apps. This gives you more granular control over your custom admin roles and helps meet your org's unique security needs. See Resource set conditions.

Biometric user verification in authentication policies

You can now configure authentication policies to require biometric user verification (no passcode). With this feature you ensure that users confirm their biometrics when they authenticate with Okta FastPass or Okta Verify Push. See Biometric user verification in authentication policies.

Automatic renewal of Okta Certificate Authorities

Okta Certificate Authorities (CAs) used for management attestation expire every five years. Without proactive renewal, expired CAs lead to disruptions in authentication and hinder compliance requirements. To mitigate this risk, the Okta CA Renewal Service automatically renews CAs 1.5 years before expiration, ensuring uninterrupted authentication and compliance. By managing CA renewals proactively, this service prevents downtime, reduces manual intervention, and guarantees that management attestation remains seamless and uninterrupted. See Okta Certificate Authority Renewal and Activation Guide

Manage Subscription button removed

The Manage Subscription button has been removed from the Settings page.

Admins prevented from deleting published app instances

When an app instance has the Published version status, admins can no longer delete it from their org.

Shared signal transmitters

Okta uses CAEP to send security-related events and other data-subject signals to third-party security vendors. To enable the transmission of signals from Okta, create an SSF stream using the SSF Transmitter API. Then, configure the third-party receiver to accept signals sent as Security Event Tokens (SETs) from Okta. See Configure a shared signal transmitter.

Early Access

Send app context to external IdPs

You can now forward context about an app to an external identity provider (IdP) when a user attempts to access the app. When you enable the Application context checkbox for an IdP, the app name and unique instance ID are included in the SAML or OpenID Connect request sent to the external IdP. This enhancement allows external IdPs to make more informed, context-aware authentication decisions, supporting advanced security scenarios, and Zero Trust environments. To enable this feature, go to Settings > Features in the Admin Console, locate Send Application Context to an External IdP, and enable.

Enrollment grace periods

Today, when admins define an enrollment policy for a group, the entire group must enroll immediately, which can be disruptive to their day-to-day tasks.

With Enrollment Grace Periods, end users can defer enrollment in new authenticators until an admin-defined deadline when enrollment becomes mandatory. This allows end users to enroll at a time convenient to them and allows for more graceful enrollment before enforcing new authenticator types in authentication policies. See Authenticator enrollment policies.

RingCentral uses new default phone number logic

The RingCentral app integration's logic for detecting and populating phone numbers has been updated to work with both DirectNumber and IntegrationNumber entries.

Single Logout for IdPs is EA in Preview

The Single Logout (SLO) for IdPs feature boosts security for organizations using shared devices and external IdPs by automatically ending IdP sessions when a user signs out of any app. This feature also requires a fresh authentication for every new user, eliminating session hijacking risks on shared devices. SLO for IdP supports both SAML 2.0 and OIDC IdP connections, which provides robust session management for shared workstations in any environment. See Add a SAML Identity Provider.

Block words from being used in passwords

You can now use Okta Expression Language to block words from being used in passwords. This feature enhances security by allowing you to customize your password strength requirements.

Fixes

SDK strings that contained iOS were parsed as unknown operating systems. (OKTA-856044)
Some UI elements on the Personal information page in My Settings had the wrong background color. (OKTA-904266)
In orgs with an embedded Sign-In Widget and the Email Optional feature enabled, users weren't prompted for their email address during self-service unlock flows. (OKTA-917289)
The /idp/myaccount/sessions endpoint didn't accept access tokens granted by custom authorization servers. (OKTA-929488)
Some users were prompted by their service provider to authenticate with Okta Verify (OV) even though they had already authenticated using OV at their identity provider. (OKTA-937311)
On the Settings page, the Technical contact field displayed a "This field cannot be left blank" error even when there was text in the field. (OKTA-939469)
In the End-User Dashboard, if a user resized the browser to a mobile-sized view, the navigation menu opened and closed repeatedly. (OKTA-940213)

Okta Integration Network

Pluto Bioinformatics is now available (SAML). Learn more.
FORA is now available (OIDC). Learn more.
Teamplify is now available (OIDC). Learn more.
XOPS is now available (API Service Integration). Learn more.

Weekly Updates

2025.6.1: Update 1 started deployment on June 23

Generally Available

Frame-ancestors rollout for Content Security Policy

Okta is rolling out the frame-ancestors directive of the Content Security Policy (CSP) for the /auth/services/devicefingerprint and /API/v1/internal/device/nonce endpoints. To prevent blocking access to these endpoints from embedded frames, add any embedder origin as a trusted origin. See Trusted Origins for iFrame embedding.

In addition, Okta is rolling out the use of nonce with the script-src directive of the CSP for the /auth/services/devicefingerprint. To prevent blocking inline scripts that you may have injected on the page returned by this endpoint, allowlist your inline script to account for the nonce addition to script-src.

New On-Prem MFA agent version

Version 1.8.3 of the On-Prem MFA agent is now available. This version includes security enhancements.

Fixes

The request.userAgent.contains("XXX") expression was supported only in authentication policies for Office 365 apps. (OKTA-827195)
Users were sometimes prompted for additional security methods from authentication method chain steps even though they weren't needed to satisfy assurance requirements. (OKTA-869644)
App logos could be added or updated using any SVG format. (OKTA-876028)
After the Okta Active Directory or LDAP agents was successfully updated, the corresponding email notification reported that zero agents were running the new version. (OKTA-876968)
Customization fields in email templates were populated with unencoded information. (OKTA-922766)
The Proxy IP Usage report returned unknown values for Proxy Type. (OKTA-930091)
Chromebook users were prompted to enroll Okta Verify on their device even though it wasn't supported. (OKTA-937063)
SAML attribute statements were incorrectly hidden on some users' custom SAML app pages. (OKTA-939543)
Users with existing sessions were prompted to authenticate with a password even though Trust claims from this identity provider was enabled on their IdP. (OKTA-947997)
The table on the HealthInsight page was misaligned. (OKTA-948682)
When the Governance for admin roles feature was enabled, admins could create custom roles with the same name as a standard role. (OKTA-950114)
Custom authenticator logos weren't displayed on the Security methods page. (OKTA-950902)
When some AD or LDAP imports failed, the warning "Incorrect result size: expected 1, actual 2" was displayed in the job UI, but no System Log message was written. (OKTA-638810)
When admins changed the prompt for authentication frequency to 1825 days (five years) in authentication policy rules, the option changed to When an Okta global session doesn't exist. (OKTA-920782)
During a full import with AD DirSync, appuser.CN was cleared, which resulted in any attributes mapped from appuser.CN to the Okta user profile being cleared. (OKTA-944122)
When an admin opened a video from the Getting Started page, the close button wasn't visible. (OKTA-946268)
Editing a previously blank default value of an attribute in the Profile Editor failed if the Attribute length was set. (OKTA-958747)
This version includes security enhancements. (OKTA-963287)

Okta Integration Network

Complyfirst.co (OIDC) is now available. Learn more.
Duo Security SCIM Provisioning (SCIM) is now available. Learn more.
Genea Access Control (SAML) is now available. Learn more.
Genea Access Control (OIDC) is now available. Learn more.
Snapshot AI (OIDC) is now available. Learn more.

2025.6.2: Update 2 started deployment on June 30

Generally Available

Sign-In Widget, version 7.32.2

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

Fixes

When a user's session expired and they tried to reauthenticate through the Sign-In Widget (second generation), an error sometimes appeared. (OKTA-805758)
Inline enrollment didn't trigger when the user clicked Sign in with Okta FastPass. (OKTA-864326)
The Report a Security Issue section appeared on the Sign-In Help page even though the End User Help Form setting was disabled. (OKTA-898824)
When an admin retried a failed Office365 provisioning task, the Immutable ID value was cleared. (OKTA-913410)
Certificate authorities for Okta Device Access didn't appear in the Admin Console after the user who created them was deleted. (OKTA-928246)
Android users couldn't authenticate using Okta FastPass after they clicked Edit Profile on the end-user settings page. (OKTA-939020)
Some users received an error when they tried to enroll in an authenticator. (OKTA-941710)

Okta Integration Network

Mailhardener (OIDC) is now available. Learn more.
Brevity (SAML) is now available. Learn more.

Version: 2025.05.0

May 2025

Generally Available

App permissions no longer include agent permissions

Realms per org limit expanded

You can now create up to five thousand realms per org. See Manage realms

Microsoft Office 365 Single Sign-on integration supports SHA-256

The Office 365 SSO integration (WS-Fed Auto and Manual) now uses SHA-256 for signing the authentication token.

New versions of Okta Provisioning agent and SDK

Okta Provisioning agent 2.3.0 and Okta Provisioning agent SDK 2.2.0 are now available. These releases contain bug fixes and minor improvements. See Okta Provisioning Agent and SDK version history.

Reasons added to System Log event

In the System Log, the Reasons field for user.risk.detect events now indicates if the detection was triggered by a DCO event.

Device assurance OS version updates

Device assurance policies now support the following OS versions:

Android 12, 13, 14, and 15 to security patch 2025-05-01
iOS 18.4.1
macOS Sequoia 15.4.1
Windows 10 (10.0.17763.7136, 10.0.19044.5737, 10.0.19045.5737)
Windows 11 (10.0.22621.5189, 10.0.22631.5189, 10.0.26100.3775)

Removal of device support for Windows 11 21H2

Okta Verify no longer supports devices that use Windows 11 21H2. See Supported platforms for Okta Verify.

Support for additional attributes in Office 365's Universal Sync

Office 365's Universal Sync now enables users to access Kerberos resources with Windows Hello for Business. See Supported user profile attributes for Office 365 provisioning

Improved Documentation Search

The search functionality on help.okta.com has been updated with the following improvements:

Localized Japanese search: Supports localized searches in Japanese for all translated content.
Focused results: Searches take place directly in Okta help instead of rerouting users to the Okta Help Center.

These features are now available on help.okta.com to help users quickly locate relevant documentation for their specific needs.

Okta Active Directory agent, version 3.20.0

This release includes support for enhanced incremental imports from AD using DirSync. Incremental import with DirSync avoids full imports and offers delta imports with AD that significantly improves performance. Configuration and opt-in is required within Okta after an agent update. This release also includes security enhancements and bug fixes. See Okta Active Directory agent version history

New protected action

Creating API tokens is now a protected action. When you enable this feature in your org, admins are prompted for authentication when they perform create an API token, at an interval that you specify. This additional layer of security helps ensure that only authorized admins can perform key tasks in your org. See Protected actions in the Admin Console.

Universal Logout for Splunk Enterprise

Splunk Enterprise now supports Universal Logout. This enables admins to automatically sign users out of this app when Universal Logout is triggered. See Third-party apps that support Universal Logout.

Policy Recommendation Tool deprecated

The trial period of the Policy Recommendation Tool has ended and the product has been deprecated.

Updates to the advanced search filters

The operators dropdown menu in the Advanced search section on people, groups and group membership pages shows all options and grays out the options that aren't applicable.

Express Configuration for OIN apps

Express Configuration lets you quickly set up SSO for OIN apps in your org. During Express Configuration, Okta and the app exchange data that's necessary to automatically set up SSO. This reduces the need for manual configuration and minimizes the chance for errors. See Add an app with Express Configuration.

ADFS version 1.8.3

Bug fixes and security hardening.

Updated text for the Login.gov IdP

For the Login.gov IdP, the Type of Identity Verification label has been updated to Type of Service Level, and the list of possible service levels has been updated.

Entitlement claims

You can now enrich tokens with app entitlements that produce deeper integrations. After you configure this feature for your app integration, use the Okta Expression Language in Identity Engine to add entitlements at runtime as OIDC claims and SAML assertions. See Generate entitlement claims using the legacy configuration.

Early Access

Advanced device posture checks

Advanced posture checks provide extended device assurance to users. It empowers admins to enforce compliance based on customized device attributes that extend beyond Okta's standard checks. Using osquery, this feature facilitates real-time security assessments across macOS devices. As a result, orgs gain enhanced visibility and control over their device fleet and ensure that only trusted devices can access sensitive resources. See Configure advanced posture checks for device assurance.

Enhanced device assurance with Android Device Trust

Android Device Trust integration for Device Assurance enhances Okta's capability to evaluate and enforce security measures on Android devices. It introduces additional security settings such as checks for Play Integrity status and Wi-Fi security. This integration strengthens device compliance while eliminating the need for Mobile Device Management (MDM), providing orgs with increased flexibility in securing their Android endpoints. See Integrate Okta with Android Device Trust.

Inline step-up flow for User Verification with Okta Verify

End users can now easily satisfy authentication policies that require higher User Verification (UV) levels, even if their current enrollment is insufficient. This feature proactively guides users through the necessary UV enablement steps. As a result, administrators can confidently implement stricter biometric UV policies to eliminate the risk of user lockouts and reduce support inquiries related to UV mismatches. See User experience according to Okta Verify user verification settings.

Breached Credentials Protection

Protect your org from the impact of credentials that have been compromised. If Okta determines that a username and password combination has been compromised after being compared to a third-party curated dataset, the protection response is customizable through password policies, including resetting the user's password, forcing a logout, or calling a delegated Workflow. See Breached credentials detection.

This feature is following a slow rollout process beginning on May 15.

Okta as an external authentication method for Microsoft Entra ID

Use Okta multifactor authentication (MFA) to satisfy Microsoft Entra ID MFA requirements. This helps users avoid double authentication and provides a seamless experience across Okta and Microsoft 365 apps. See Configure Okta as an external authentication method for Microsoft Entra ID .

DirSync group imports for Active Directory

For Active Directory (AD) integrations, the Provisioning tab now provides an Enable imports with AD using DirSync checkbox. When you enable the checkbox, admins can perform incremental group imports using DirSync. See Configure Active Directory import and account settings.

Custom admin roles for ITP

Through this feature, customers can use granular ITP permissions and resources to create custom roles to right-size authorization for ITP configuration and monitoring. See Configure custom admin roles for ITP.

Fixes

Users were sent to the wrong help topic when they clicked Learn more in the Change Password section of the end-user Settings page. (OKTA-801189)
Admins who tried to create a stream with an inaccessible URL received an Internal Server Error (HTTP 500) instead of an API Validation Error (HTTP 400). (OKTA-827169)
Users who signed out of the End-User Settings version 2.0 page were redirected to their sign-in page instead of their custom sign-out page. (OKTA-878856)
When a custom admin role had the Generate device recovery PIN permission, admins with that role couldn't create a recovery PIN for a Desktop MFA client. (OKTA-881842)
When accessing an Okta org2org application on macOS devices, some users were unnecessarily prompted to enroll in the Okta Verify app. (OKTA-882059)
When doing incremental imports using Okta Provisioning agent, users whose profiles weren't modified were removed from groups in Okta. (OKTA-884952)
Admins and users couldn't reset the password for staged accounts with an unverified email status. (OKTA-885853)
The border for the table of Active Directory instances on the Delegated Authentication page was missing. (OKTA-893589)
When authenticating with SMS or Google Authenticator, some users saw an incorrect error message when they entered a space in the Enter code field of the Sign-In Widget (third generation). (OKTA-897996)
When admins enabled the Unified Look and Feel for Okta Admin Console feature, some user interface elements didn't render correctly on Default Policy pages. (OKTA-903370)
When users enrolled in Okta Verify, the core.user.factor.activate System Log event wasn't recorded. (OKTA-908444)
Some users were asked repeatedly to approve multiple Okta FastPass user verification prompts. (OKTA-909450)
Users were prompted for multifactor authentication twice when they signed in to a spoke org in an Okta Org2Org scenario even though the Trust claims from this identity provider option was selected for the hub org. (OKTA-912172)
Some users saw a login hint in the UserHome page URL for OIDC apps even though login hints were disabled. (OKTA-919432)
Super admins couldn't always access Workflows with the role-based access control (RBAC) feature enable. (OKTA-920704)
When third-party IdP claims sharing was enabled, the redirect to the IdP happened during reauthentication even if IdP didn't provide any AMR claims. (OKTA-922086)
PERIMETER81_VPN was incorrectly announced as a supported IP service category in enhanced dynamic zones. (OKTA-923426)
When a call to activate a downstream app user failed while activating a user, the user was stuck in an activating status. (OKTA-925217)
The user's profile dropdown menu label displayed the user's email address instead of their first name in the Secure Partner Portal app. (OKTA-925251)
If a third-party SAML IdP sent the session.amr SAML attribute without the attribute schema type, Okta rejected the response when the third-party claims sharing feature was enabled. (OKTA-925864)
Starting with version 136, Chrome no longer returned the thirdPartyBlockingEnabled signal, and users whose Device Assurance policies relied on the signal were denied access to their resources. (OKTA-927884)

Okta Integration Network

JoVE (SAML) is now available. Learn more.
Partner Element (OIDC) is now available. Learn more.

Weekly Updates

2025.5.1: Update 1 started deployment on May 19

Generally Available

On-Prem MFA agent, version 1.8.2

Version 1.8.2 of the On-Prem MFA agent is now available. This version includes security enhancements.

Sign-In Widget, version 7.31.1

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

Sign-In Widget, version 7.31.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.

New filter and columns for Access Certifications reports

You can use the Campaign ID filter in the Past campaign details and Past campaign summary reports. You can find a campaign's ID from System Log events or from the URL for the campaign details page. Additionally, the following columns are available for use in the Admin Console.

Past campaign details report:
- User email
- Reviewer email
- Reviewer reassigned
Past campaign summary report:
- Campaign resource count

Fixes

Some System Log entries showed the wrong user agent operating system version for risk scoring and new device detection events. (OKTA-792841)
Some Active Directory Single Sign-On (ADSSO) users were required to provide their username in the Sign-In Widget before they were routed to ADSSO. (OKTA-814881)
The Application Usage report didn't include successful RADIUS authentications. (OKTA-815504)
Some users didn't receive emails from Okta. (OKTA-826144)
When users edited an authorization server on the Security > API page, the value of the Type column on the Claims tab incorrectly wrapped to a second line. (OKTA-863707)
Some users weren't prompted for multifactor authentication after the Keep me signed in period expired. (OKTA-871178)
Admins didn't receive the correct notifications when they had both role and admin email notifications selected. (OKTA-876846)
Some ADSSO functionality didn't work as expected. (OKTA-880273)
When users edited an authorization server on the Security > API page, some user interface elements had the wrong background color. (OKTA-893509)
Some user interface elements on the API Token page had the wrong background color. (OKTA-893608)
Some users saw an extra line at the bottom of the Identity Providers page. (OKTA-893613)
Some user interface elements in the Access Testing Tool didn't render correctly when the Unified UI for the Admin App feature was enabled. (OKTA-904105)
Some user interface elements in the entity risk policy didn't render correctly when the Unified UI for the Admin App feature was enabled. (OKTA-904369)
Some user interface elements had incorrect spacing on the Okta API Scopes tab of app pages. (OKTA-905018)
Email notifications for the super admin role weren't applied consistently when all admin email notification settings were selected for the role. (OKTA-906587)
Agents in an error state were properly displayed on the Agent Monitors page for their respective directory integration but weren't displayed on the Admin Dashboard. (OKTA-910056)
Some users received an error message when they tried to sign in after their account was unlocked. (OKTA-913228)
Some users were prompted for multifactor authentication despite having previously selected Stay signed in. (OKTA-914076)
On the Add resource dialog, the Show more button didn't display all the resources that were already included in the resource set. (OKTA-921890)
Starting with version 136, Chrome no longer returned the thirdPartyBlockingEnabled signal, and users whose Device Assurance policies relied on the signal were denied access to their org. (OKTA-927884)
After signing in to Okta on a mobile device (either Android or iOS), opening the menu resulted in the screen flickering. (OKTA-933477)
Some users were unable to authenticate using Microsoft Entra ID External Authentication Methods. (OKTA-936300)
Updating an LDAP-sourced user profile sometimes resulted in an error. (OKTA-939330)

Okta Integration Network

Attribute Dashboard (OIDC) now supports IdP-initiated SSO flows.
DX (SAML) is now available. Learn more.
Embrace (SAML) is now available. Learn more.
Merkle (OIDC) is now available. Learn more.
SAP Concur by Aquera is now available. Learn more.
SAP S/4HANA by Aquera (SCIM) is now available. Learn more.

2025.5.2: Update 2 started deployment on May 27

Fixes

The online help link on the Brands page didn't link to the correct page. (OKTA-654709)
Some users saw an error message when editing the Embedded widget sign-in support settings on the Settings > Account page. (OKTA-881712)
LDAP agents were displayed as operational after registration, even if they hadn't successfully connected to Okta. (OKTA-886963)
Some users were prompted to enroll in additional authenticators after they enrolled in the FIDO2 (WebAuthn) authenticator. (OKTA-888797)
Some user interface elements in pages under the Customizations menu didn't render correctly when the Unified UI for the Admin App feature was enabled. (OKTA-893521)
The border on the Delegated Authentication page for LDAP used squared corners instead of rounded corners. (OKTA-893569)
When some users requested a new account activation email, an error message appeared after they clicked Request activation email. (OKTA-919395)
Some user interface elements on app pages weren't rendered correctly. (OKTA-932378)
Some pages didn't load correctly when the Unified look and feel for Okta Admin Console feature was enabled. (OKTA-938750)

Okta Integration Network

CyberDefenders (OIDC) is now available. Learn more.
Google Cloud Workforce Identity Federation (OIDC) is now available. Learn more.
Pro-Vigil (SAML) is now available. Learn more.

2025.5.3: Update 3 started deployment on June 2

Generally Available

RingCentral uses new default phone number logic

The RingCentral app integration's logic for detecting and populating phone numbers has been updated to work with both DirectNumber and IntegrationNumber entries.

Integrator Free Plan org now available

The Integrator Free Plan org is now available on the Sign up page of the developer documentation site. These orgs replace the previous Developer Editions Service orgs, which will start being deactivated on July 18th. See Changes Are Coming to the Okta Developer Edition Organizations. For information on the configurations for the Integrator Free Plan orgs, see Okta Integrator Free Plan org configurations.

Fixes

Users who successfully authenticated with AMR claims were still prompted to stay signed in. (OKTA-914125)
Users with '+' in their email address couldn't reset their passwords from email templates. (OKTA-914601)
When an admin changed a user attribute in Okta, the profile in Zendesk reverted back to the default language of the Zendesk account. (OKTA-916240)
In the System Log, 'policy.evaluate_sign_on' events with a DENY outcome displayed a 'PolicyRuleFactorMode'. (OKTA-922161)
Some users incorrectly received an Invalid Phone Number error when they enrolled an SMS factor. (OKTA-923373)
When an admin configured the Salesforce.com connector with the Customer Portal user type and then ran an import, no users were fetched. (OKTA-931016)
When using an Org2Org integration between a Classic hub org and an OIE spoke org, some users were prompted for MFA in the spoke org even though Trust claims from this identity provider was enabled and they had already authenticated in the hub org. (OKTA-931086)
After signing in to Okta on a mobile device (either Android or iOS), opening the menu resulted in the screen flickering. (OKTA-933477)
When users performed Org2Org SSO with an existing IdP session, FactorVerifiedByIdp was missing from the System Log entry. (OKTA-935626)
When third-party IdP claims sharing was enabled, some claims were missing from the System Log. (OKTA-936530)
Some UI elements rendered incorrectly on the Security Methods section of the Settings page on the End-User Dashboard. (OKTA-937390)
Some pages didn't load correctly when the Unified look and feel for Okta Admin Console feature was enabled. (OKTA-938750)
Updating an LDAP-sourced user profile sometimes resulted in an error. (OKTA-939330)
When the Enforce MFA for admin-only Identity Governance apps feature was enabled, the authentication policy settings were hidden from the Application pages. (OKTA-939580)
When third-party claims sharing was enabled, users couldn't sign in using their IdP because of an authentication loop. (OKTA-939862)
Search functionality didn't work in the AAGUID list table. (OKTA-940240)

Okta Integration Network

Conviva (SCIM) is now available. Learn more.
Paylocity (Demo)(SCIM & SAML) is now available. Learn more.
SELR.ai (OIDC) is now available. Learn more.
Wirespeed (API service) is now available. Learn more.