Okta Identity Engine release notes (Production)

Version: 2025.11.0

November 2025

Generally Available

Manage agents permission granted to certain roles

Custom admin roles with the View application and their details permission now have the View agents permission. This is a temporary change that helps Okta separate the two permissions in a future release. See Role permissions.

New System Log event for AD agent changes

The System Log event system.agent.ad.config.change.detected reports when Okta support modified an AD agent configuration. (OKTA-1047077)

Express Configuration supports Universal Logout

Admins can now quickly integrate Universal Logout-enabled apps using Express Configuration. When Universal Logout is available for an Express Configuration app, a Configure SSO & UL button appears on the configuration page. See Add an app with Express Configuration.

Custom domains and certificates

Okta now supports the use of SHA 384 and SHA 512 signed certificates for custom domains. See Configure a custom domain.

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

Partner Admin Portal App Switcher

In the Partner Admin Portal, you can now use the App Switcher to navigate to your apps.

Okta Active Directory agent, version 3.22.0

This release includes LDAPS support and bug fixes. See Okta Active Directory agent version history.

Remember last-used authenticator: Okta FastPass

Okta now remembers FastPass as the last-used authenticator when users click "Sign in with Okta FastPass" on the Sign-In Widget.

Simplified Windows Autopilot integration

You can use Okta to secure and streamline the Windows Autopilot flow on end-user devices. You can add a sign-on policy rule in Okta that requires MFA when enrolling a device through Windows Autopilot. This increases security without compromising the user experience and ensures that every new device is provisioned by the right user. See Typical workflow for using Okta with Windows Autopilot.

ITP landing page

Previously, Identity Threat Protection with Okta AI (ITP) information and controls were nested across various pages of the Admin Console. All of your ITP insights and controls are now consolidated on the Security tab in the Admin Console. This unified view saves you time and enables faster action by allowing you to investigate data and configure a response, all in a single place. See Identity Threat Protection with Okta AI.

Inline FastPass enrollment on multiple devices

Users can complete inline enrollment of Okta Verify when they have already enrolled in Okta Verify on a different device platform using a different method.

Network restrictions for OIDC token endpoints is GA in Production

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

Export Okta Identity Governance reports in PDF format

You can now export Okta Identity Governance reports to PDF. When exporting, you can also select specific columns to include in the report.

Behavior Detections for new ASN

Admins have been able to create behavior detections for IP, Velocity, Location, or Device. This new functionality introduces behavior detection on a new ASN (Autonomous System Number), based on the IP found in the request tied to the event. See Add an ASN behavior.

Temporary Access Code authenticator

The Temporary Access Code (TAC) authenticator allows admins to generate temporary codes that let users authenticate in onboarding, account recovery, and other temporary access scenarios. This authenticator enhances security in these scenarios by granting users access to their orgs without having to use their usual authenticators. See Configure the temporary access code authenticator.

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.

Enhanced security for Okta Access Requests web app

The Okta Access Requests web app now performs policy evaluations before granting new access tokens.

Early Access

Password complexity requirements

Okta now lets you limit the number of consecutive repeating characters that users can put in their passwords. Password complexity requirements are now also applied to Active Directory and LDAP-sourced users. This change enhances the security of your org by expanding password complexity options, and applying this protection to more user profile types. See Configure the password authenticator.

New custom admin permissions

New custom admin permissions let you read or read and write in app sign-in, global session, and Okta account management policies. This enhances the granularity of admin permissions in your org. See Create a resource set.

Submit entitlement management integrations

Independent Software Vendors (ISVs) can now submit SCIM 2.0-based entitlement management integrations to the Okta Integration Network (OIN). This enhancement enables customers and IT admins to discover, manage, and assign fine-grained entitlements such as roles and permissions directly from Okta. By standardizing entitlement management, organizations can automate access assignments and streamline Identity Governance, ensuring users receive the right access and roles without manual intervention. For more information, see Submit an integration with the OIN Wizard.

Device Assurance for Windows: Virus and threat protection

Admins can now enforce a Device Assurance condition that requires Windows devices using the Chrome browser to have virus and threat protection enabled. This self-service EA feature strengthens your org's security posture by ensuring that user devices are protected by active antivirus software before granting access.

User enumeration prevention enhancement

Admins can now configure which authentication methods users are prompted for when they sign in from an unknown device or browser and trigger enumeration prevention. This enhances org security by adding more protection to sign-in attempts. See General Security.

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 based on Okta Verify user verification settings.

Fixes

  • An Okta Verify error prevented some users from signing in to orgs that had the Advanced Posture Check feature enabled. The error wasn't recorded in the System Log. (OKTA-897459)

  • Some users saw incorrectly rendered dropdown menus that persisted between screens. (OKTA-955890)

  • When an app sign-in policy included an authentication method chain, users who enrolled Okta Verify on another device couldn't complete inline enrollment into Okta Verify on a second device using a different authentication method. (OKTA-908311)

  • Some users could unlock their accounts even though this wasn't allowed in password policies. (OKTA-984362)

  • In orgs with the Send Application Context to an External IdP feature enabled, users couldn't access apps if the app names had trailing whitespaces. (OKTA-998869)

  • AD password resets sometimes failed with an exception. (OKTA-1004233)

  • When interacting with the Access Request web app using Safari browser, users couldn't tag another user with @ in the request's chat. (OKTA-1005685)

  • When a phishing attack was detected, the System Log didn't always record the event. (OKTA-1006043)

  • Deleted request types sometimes reappeared if the org had the Unified Requester Experience feature enabled. (OKTA-1040545)

  • When the LDAP agent installer successfully registered the agent but the installation failed, the agent incorrectly appeared as operational. (OKTA-1045661)

Okta Integration Network

  • Harmony now has the okta.users.manage, okta.groups.read, and okta.groups.manage scopes.

  • Valos (OIDC) has a new redirect URI. Learn more.

  • Chronicle of Higher Education (SWA) was updated.

  • 1VALET (SAML) has updated attribute statements.

  • Fabrix Smart Actions (API Service) now has the okta.groups.manage scope.

  • Boston Properties (SWA) was updated.

  • Holistiplan SSO (SAML) is now available. Learn more.

  • Mimecast Human Risk Integration (API Service) is now available. Learn more.

  • Aglide (SAML) is now available. Learn more.

  • Aglide (SCIM) is now available. Learn more.

  • SmarterSign Digital Signage (OIDC) is now available. Learn more.

  • SmarterSign Digital Signage (SCIM) is now available. Learn more.

Version: 2025.10.0

October 2025

Generally Available

Changes to access request notifications

To ensure conversations are displayed consistently across platforms, messages sent within an access request from the web app now automatically appear for the message sender in the corresponding Slack or Microsoft Teams thread. This reduces confusion for the message sender around the messages associated that are with a request.

Okta Provisioning agent, version 3.0.4

Okta Provisioning agent 3.0.4 is now available. This release contains bug fixes and minor improvements.

Simplified Windows Installer for Okta Provisioning agent

The Windows Installer UI for the Okta Provisioning agent has been simplified. The environment selection dropdown list has been removed to support a wider range of Okta environments.

Device assurance OS version update

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

  • iOS 18.7.1
  • iOS 26.0.1
  • macOS Sonoma 14.8.1
  • macOS Sequoia 15.7.1
  • macOS Tahoe 26.0.1

Detections added to entity risk policy

New detections have been added to the entity risk policy.

  • Suspicious Login From An IP Flagged By FastPass: Indicates a sign-in event occurred from an IP address that Okta FastPass flagged in a phishing event.

  • Suspicious Login From An IP Flagged In A Credential Based Attack: Indicates a successful sign-in event occurred from an IP address where multiple sign-in failures also occurred.

  • Breached Credentials Detected: Indicates that a username-password combination in your org appears in a third-party list of public data breaches.

See Detection settings for entity risk policy.

Okta Active Directory Password Sync agent, version 1.7.0

This version of the agent includes security enhancements.

Trace ID added to event

A traceId has been added to the security.breached_credential.detected System Log event so that you can easily query and link ITP events like user.risk.detect and ERP events in system logs.

New look and feel for delegated flows

On the Delegated flows page, the buttons, modals, and input fields have been redesigned for a better user experience. See Delegated flows.

Euskara (Basque) language translations for end users

In the End-User Dashboard, users can now set the display language to Euskara (Basque). When they select a language, the end-user experience, including when a user signs in, is translated accordingly. See Supported display languages.

New VPN service for enhanced dynamic zones

The SURF_EASY_VPN is now supported as an individual VPN service category in enhanced dynamic zones. See Supported IP service categories.

Error message update

The error message text that appears when activating a group rule that has an invalid expression has been updated to include the reason for the failure, making it easier to troubleshoot.

Create user permission conditions

You can now add conditions to the Create user permission for custom admin roles, applicable to both realm-enabled orgs and those without realms. See Permission conditions.

User status in Okta Expression Language

You can now reference User Status in the Okta expression language. Group Rules can leverage user statuses to drive group membership.

SharePoint On-Premises integration supports SHA-256

SharePoint integrations (WS-Fed) now use SHA-256 for signing the authentication token.

Group Push Linking for Microsoft Office 365

The Group Push feature in the Microsoft Office 365 integration has been enhanced to link existing Okta groups with existing Entra groups.

This change establishes Okta as the single source of truth for group membership. Once linked, the membership changes made in Okta are pushed automatically, ensuring consistency and seamless access control.

Supporting additional attributes in O365's Universal Sync provisioning

To enable seamless access to Kerberos resources through Windows Hello for Business and to help you manage data based on geographies, Okta now supports four additional attributes in O365's Universal Sync provisioning.

  • onPremisesSamAccountName
  • onPremisesDomainName
  • onPremisesUserPrincipalName
  • PreferredDataLocation

Changes to the Session Protection Violation report

A filter has been added to the Session Protection Violation report that allows filtering on risk level (LOW, MEDIUM, HIGH). Also, the Session Context Change count has been removed from the report.

Okta Integration IdP type

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.

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.

Behavior Detections for new ASN

Admins have been able to create behavior detections for IP, Velocity, Location, or Device. This new functionality introduces behavior detection on a new ASN (Autonomous System Number), based on the IP found in the request tied to the event. See Add an ASN behavior.

Early Access

User password migration from AD to Okta

Seamlessly migrate user passwords from AD to Okta without disrupting your users or operations. This establishes Okta as the source of truth for user passwords, enabling it to handle user authentication and eliminating the need for delegated authentication. See Password migration from AD to Okta

Protected action support for device signal collection policies

Okta prompts for step-up authentication when admins make changes to device signal collection policies in the Admin Console. The changes are only allowed after the admin authenticates successfully. This feature enhances org security by allowing admins to require MFA before performing protected actions. See Protected actions in the Admin Console.

Fixes

  • Users found accessibility issues in the Sign-In Widget (third generation) error messages, SVG icons, and the show/hide password toggle. (OKTA-867363)

  • Sometimes, inactive apps that had provisioning enabled sent deprovisioning calls to downstream apps. (OKTA-930436)

  • Sometimes, users who were assigned an app were unable to view or access the app on their End-User Dashboard. (OKTA-985663)

  • Some users saw a Conflicting App User IDs specified on state token error message when they tried to sign in to an OIDC app using the embedded Okta Sign-In Widget. (OKTA-992348)

  • SAML assertions were encrypted if they included the oktaAuthPayload parameter even though encryption wasn't enabled on the app. (OKTA-998820)

  • If the "End-user remediation for management attestation" feature was enabled and an admin had also configured a custom access denied error message, users were shown the custom error message instead of the remediation steps in the Okta Sign-In Widget. (OKTA-1008850)

  • In some orgs with the Unified claims generation for Okta-protected SAML and OIDC custom app integrations early access feature enabled, users were unable to use the dropdown menus in the Attribute Statements > Show legacy configuration section of the app page. (OKTA-1010898)

  • When an OIDC app had an authentication policy with a rule that includes device assurance through a Chrome device trust connector, users received an error when accessing the app through a sign-in URL configured with prompt=none. (OKTA-1016620)

  • In orgs with the Custom Password Policy Restrictions early access feature enabled, some admins saw an incorrect error message when they selected Use an OEL statement to block restricted content and entered an expression. (OKTA-1027968)

  • In orgs with Japanese translations, untranslated text appeared on the Active Directory Policy page. (OKTA-1029000)

  • In orgs with the Custom Password Policy Restrictions early access feature enabled, some admins saw an Internal Server Error message when they tried to reset a user's password using a temporary password. (OKTA-1030190)

Okta Integration Network

  • Paychex Online was updated.

  • Ravenna is now available (API Service Integration). Learn more.

  • zkipster was updated.

Doc Updates

Okta Aerial documentation

Documentation for Okta Aerial has been added to help.okta.com with the following updates:

  • Aerial card added to the home page.
  • Aerial option added to Documentation dropdown list.
  • Aerial release notes added to Release notes dropdown list.

Okta Aerial allows you to manage multiple Okta orgs from a single, centralized account. The Aerial account lives outside of your other orgs and can manage any Production or Preview org that's linked to the Aerial account. Each Aerial account has a dedicated Aerial org where you can invite Aerial admins who can request and be granted access to connected orgs in your environment. See Okta Aerial.

Weekly Updates

2025.10.1: Update 1 started deployment on October 13

Generally Available

Recent searches displayed in search field

Now when you select the Admin Console search field, a list of your recent searches appears. This helps you quickly find the users, apps, and groups that you frequently search for.

Custom IDV vendors

Okta now supports using custom identity verification (IDV) vendors as identity verification providers. This enhances the security of account onboarding or recovery and mitigates the risk of identity fraud by adding additional verifications of the person setting up or recovering the account. See Add a custom identity verification vendor.

New IP service categories supported

There are new IP service categories for network zones supported by Okta. See Supported IP service categories for a complete list.

Fixes

  • When users accessed the Microsoft ADFS app and authenticated with Okta Verify, the System Log didn't show the app name in the Targets column. (OKTA-906244)

  • Admins couldn't delete their custom IdP authenticator if the IdP that the authenticator was being used in had already been deleted. (OKTA-987328)

  • The authentication policy UI was missing a clarifying message for the generic "Custom OTP" authenticator label. (OKTA-1003291)

  • The System Log didn't display failed authentication attempts when they were initiated from SAML apps with external IdPs. (OKTA-1014150)

  • In orgs with JIT enabled, staged Active Directory (AD) users were prompted to change their password even it wasn't required by their org's AD password policy. (OKTA-1020693)

  • Some admins couldn't use Single Logout for generic OIDC IdPs because the Okta IDX cookie exceeded browser size limits. (OKTA-1024848)

  • Users saw an error message when they tried to use their passkey to sign in to their Okta domain and a custom domain. (OKTA-1025465)

  • Sometimes multiple duplicate group.user_membership.remove System Log events were fired when a user was removed from a group. (OKTA-1031604)

  • When a user signed in or out of an org with Single Logout enabled, the loading screen had the wrong background color. (OKTA-1036274)

  • When the AD DirSync feature was enabled but not configured, AD group membership removals weren't reflected in Okta following an incremental import. (OKTA-1040614)

Okta Integration Network

  • Exaforce has a new integration guide and additional use cases.

  • Ravenna is now available (API Service Integration). Learn more.

  • Grafana Labs is now available. Learn more.

  • Realty.com Portal (OIDC) is now available. Learn more.

  • Realty.com Portal (SCIM) is now available. Learn more.

2025.10.2: Update 2 started deployment on November 3

Generally Available

Okta Provisioning agent, version 3.0.5

Okta Provisioning agent 3.0.5 is available. The httpConnectionTimeoutInMs and httpSocketTimeoutInMs properties are now configurable to meet your specific requirements.

New IP service categories

PLAINPROXIES_PROXY, FINE_VPN and URBAN_VPN are now supported as IP service categories in enhanced dynamic zones. See Supported IP service categories for a complete list.

Improved LDAP Interface UI

The client ID is no longer displayed on the LDAP Interface app.

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

Sign-In Widget, version 7.36.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 token encryption was enabled for an app or authorization server, the System Log didn't record when a token was successfully minted. (OKTA-954232)

  • The authentication policy UI was missing a clarifying message for the generic "Custom OTP" authenticator label. (OKTA-1003291)

  • User sync to O365 failed if the Usage location was updated after the license was assigned. (OKTA-1017269)

  • Users' metadata wasn't updated after they authenticated through AD delegated authentication. (OKTA-1031477)

  • The LegacyIPZone wasn't saved if gateway IPs and trusted proxy IPs were empty. (OKTA-1032603)

  • Users' cursors were placed in the Username field of the Sign-In Widget by default, instead of the Password field. (OKTA-711623)

  • Some UI elements on the Identity Providers page weren't in the correct location. (OKTA-904304)

  • In Workflows, the Okta Connector app didn't display a list of available connector actions. (OKTA-946866)

  • When the Trust Claims from IdP setting was enabled for an identity provider and used with a custom Okta Account Management Policy rule, users received an internal server error when they tried to enroll a new authenticator. (OKTA-962495)

  • Admins couldn't clone authentication policies that used disabled authenticators. (OKTA-967255)

  • The session protection policy evaluation failed for some unregistered devices. (OKTA-1013026)

  • Okta incorrectly presented user verification challenges to users who weren't allowed to reset their passwords after they clicked Forgot password?. (OKTA-1020725)

  • The Add Resource dialog didn't display resources that had three or fewer characters. (OKTA-1030065)

  • When admins tried to add new values to the attributes in a user profile, the system failed to save the changes. (OKTA-1037440)

Okta Integration Network

  • IdentiGuard (API Service Integration) is now available. Learn more.

  • ChatFin (OIDC) is now available. Learn more.

  • Rowan Security (OIDC) is now available. Learn more.

  • Biome SCIM (SCIM) is now available. Learn more.

  • Qualified.io (SCIM) is now available. Learn more.

  • Meraki was updated.

  • Qualified.io (SAML) has a new icon and integration guide. Learn more.

  • Exaforce has a new integration guide and additional use cases.

  • Ariba Network (SWA) was updated.

Version: 2025.09.0

September 2025

Generally Available

Translations update for the Partner Admin Portal

Japanese translations for the Add user and Edit user forms have been updated. This change aligns the Japanese labels with their English counterparts.

Office 365 License and Roles Management now supports sync entitlements

Sync entitlements are now supported for the Office 365 License and Roles Management provisioning type in orgs with Identity Governance enabled.

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

Improved user experience for Access Requests

The access request details page has been improved to provide more visibility on tasks assigned approvers and answers submitted by requesters. If you integrated Slack or Teams with Access Requests, similar changes have been made to the access request message that approvers receive. Additionally, the email notification sender's name and address have been changed. The sender's name is Okta Access Requests and the email address is noreply@at.okta.com.

New versions of Okta Provisioning agent and SDK

Okta Provisioning agent 3.0.3 and Okta Provisioning agent SDK 2.4.0 are now available. These releases contain bug fixes and minor improvements.

Improved search in the Partner Admin Portal

The Partner Admin Portal user list now sorts by the Last Updated column in descending order by default. The search feature uses a Contains operator for three or more characters.

Device assurance OS version update

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

  • Android 13, 14, 15, 16 security patch 2025-09-01
  • iOS 18.6.2
  • iOS 26.0.0 (major version)
  • macOS Ventura 13.7.8
  • macOS Sonoma 14.7.8
  • macOS Sequoia 15.6.1
  • macOS Tahoe 26.0.0 (major version)
  • Windows 10 (10.0.17763.7678, 10.0.19044.6216, 10.0.19045.6216)
  • Windows 11 (10.0.22621.5768, 10.0.22631.5768, 10.0.26100.4946)

The following versions are no longer supported:

  • iOS 15.8.4
  • iOS 16.7.11
  • macOS 12.7.6
  • Windows 11 (10.0.22000.3260)

Nonce rollout for Content Security Policy

Okta is rolling out nonces for the style-src directive of the Content Security Policy for every endpoint that returns html content. This is a two stage process: first, the nonce is added to the Content-Security-Policy-Report-Only header style-src directive; later, after any unsafe inline instances are identified and fixed, the nonce is added to the Content-Security-Policy header style-src directive. This update will be gradually applied to all endpoints.

These updates will be applied to Okta domains and custom domain pages that aren't customizable by admins (for example, sign-in pages, and error pages on custom domains). See Customize an error page.

Export Admin Console reports in GZIP format

You can now export most Admin Console reports in GZIP format, in addition to the existing CSV format. GZIP exports have a higher row limit (30 million) and a smaller file size.

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 protection.

This feature is following a slow rollout process.

Assigning/revoking an admin role is a protected action

Now when an admin assigns or revokes an admin role from a user, they're prompted for additional authentication. See Protected actions in the Admin Console.

API service apps

API service apps are no longer assigned to the shared default app sign-in policy when they're created. See App sign-in policies.

Authentication policy UI updates

Authentication policies have been renamed and are now known as "app sign-in policies." The term "authentication policies" now refers to a group of policies: app sign-in policies, the Okta account management policy, and the session protection policy. UI enhancements have also been made to these pages to improve navigation and user experience. See App sign-in policies.

New option to clear "keep me signed in"

When revoking a user's IdP sessions and refresh tokens in the Clear sessions and revoke tokens dialog, admins can now choose whether or not to use the Clear "keep me signed in" option.

Admin Console Realm updates

The hint text for the Realm dropdown on the Add User form has been updated to provide clearer instructions.

Secure Identity Integrations filters in the OIN catalog

The Browse App Integration Catalog page now provides three new Secure Identity Integrations checkboxes: Secure Identity Integrations - Fundamental, Secure Identity Integrations - Advanced, and Secure Identity Integrations - Strategic. When you select one, the OIN catalog displays only the apps with that specific functionality.

New System Log target

The Authentication Enrollment Policy target was added to the 'policy.evaluate_sign_on' System Log event. This change makes it easier for admins to identify the policy that was involved in user sign-in attempts.

LDAP Interface OIDC app

LDAP Interface now has an app sign-in policy that only enforces password. This only applies to Okta orgs without a prior LDAP interface setup. For orgs with an existing LDAP interface setup, global session policies still control LDAP Interface authentication policies. See Set up and manage the LDAP Interface. The session length for OpenID Connect (OIDC) connections is now limited to one hour. After the session expires, a new BIND operation is required to continue performing SEARCH queries on the same connection. You may need to update existing scripts to account for this enforced session length.

Map unknown platform to desktop

Okta now maps unrecognized platform conditions to Other desktop. Previously, unrecognized platform conditions matched correctly only when the Any platform condition was selected in the app sign-in policy.

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.

Child Domain Authentication for Office 365 WS-Federation

Office 365 WS-Federation automatic configuration now supports child domain authentication. See Federate multiple Office 365 domains in a single app instance.

App Switcher for Okta first-party apps

The End-User Dashboard, Admin Console, and Workflows Console now have an App Switcher that helps admins quickly navigate between their assigned Okta apps. Note that you must enable the Unified look and feel for Okta Admin Console and Unified look and feel for Okta Dashboard Early Access features for the App Switcher to appear.

New change password feature for end users

The Security methods page in My Settings now allows end users to change their password.

Custom remediation for device assurance

You can now display custom remediation instructions to users when authentication fails due to unsuccessful device posture checks with Okta Verify or Chrome Device Trust. See Configure custom remediation instructions for device assurance.

Early Access

Desktop MFA recovery for Windows

This release enhances the Desktop MFA feature on Windows to include an admin-assisted recovery path. If a user is locked out of their Windows device, an admin can now issue a time-based recovery PIN. This grants the user temporary access to their computer without needing their primary MFA device, enabling them to resolve their authenticator issue and sign in successfully. See Enable Desktop MFA recovery for Windows.

End-user remediation for management attestation

This enhancement improves Okta's custom error remediation by extending it to management attestation across all OS platforms. Admins can now create specific remediation messages for devices that fail a management check (for example, their device is not MDM-managed). Users receive clear, actionable remediation instructions during the sign-in flow, and can troubleshoot problems independently. This leads to fewer IT helpdesk tickets, faster secure access, and a better user experience. See Remediation messages for device assurance.

More Universal Directory attributes available for identity verification mapping

Admins can now map more Universal Directory attributes 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 IDV vendor. See Add a pre-configured identity verification vendor.

Passkey and security key subdomain support

Okta now lets users authenticate with their passkeys or security keys in their Okta org or custom domain, and all subdomains below them. This helps you achieve phishing-resistant authentication and avoids the need to issue multiple passkeys or security keys to each user for each domain they access. See Configure the FIDO2 (WebAuthn) authenticator.

Anything-as-a-Source for groups and group memberships

Anything-as-a-Source (XaaS) capabilities allow customers to use a custom identity source with Okta. With XaaS, customers can connect custom HR apps or custom databases to source users into Okta's Universal Directory.

This release offers XaaS capabilities with groups and group memberships, allowing customers to start sourcing groups with XaaS. Okta now enables creating and updating users, creating and updating groups, and managing group memberships into Okta's Universal Directory from any identity source using XaaS APIs. See Anything-as-a-Source.

Fixes

  • Some users received an error message when they reset their passwords on mobile devices that didn't have Okta Verify installed, even though the password reset was completed. (OKTA-958340)

  • In some orgs with an Okta Org2Org integration, users were unable to access bookmark or Org2Org apps from the spoke org, even though they had permission to use the app. (OKTA-981462)

  • Some users received an error message instead of an account unlock challenge when User Enumeration Prevention was turned off. (OKTA-993341)

  • In the Partner Admin Portal, the chevron icon in the sidebar wasn't correctly aligned. (OKTA-1003466)

  • When a user signed in to a custom domain and then clicked Admin in the App Switcher, they were sometimes presented with the wrong sign-in flow. (OKTA-1014174)

Okta Integration Network

  • AmexGBT Egencia has a new app name, icon, and SAML Integration guide. Learn more.

  • ZAMP (OIDC) has two new redirect URIs. Learn more.

  • Harmony (API Service Integration) is now available. Learn more.

  • Shift Security (API Service Integration) is now available. Learn more.

  • Teem Finance (OIDC) is now available. Learn more.

  • Island (Universal Logout) is now available. Learn more.

  • CloudEagle (API Service Integration) was updated.

  • Bruin was updated.

  • EventNeat (OIDC) is now available. Learn more.

  • AdvancedMD was updated.

  • Nuclei (OIDC) is now available. Learn more.

  • FloQast (SCIM) is now available. Learn more.

  • Astrix Security Monitoring (API Service Integration) is now available. Learn more.

  • Scrut Automation (OIDC) has a new Redirect URI.

  • Canva (SWA) was updated.

  • eSignon (SAML) is now available. Learn more.

  • eSignon (SCIM) is now available. Learn more.

  • AmexGBT Egencia (SCIM) is now available. Learn more.

Weekly Updates

2025.9.1: Update 1 started deployment on September 29

Generally Available

Enhanced protection for Google group imports

A safeguard has been added to prevent accidental data loss during group imports from Google. When a large volume of group deletions is detected, the import is stopped to protect against importing bad data.

Removed delegate self-approval for Access Requests

Delegates can no longer approve requests made on their behalf, ensuring proper separation of duties.

Okta Provisioning agent SDK, version 3.0.3

This release contains security enhancements and support for JDK 17. See Okta Provisioning agent and SDK version history.

New functionality filters in the OIN

The Browse App Integration Catalog page now provides Cross App Access and Privileged Access Management functionality filters. The new filters help admins quickly find Cross App Access- and Privileged Access Management-enabled apps in the OIN.

Fixes

  • System Log entries weren't recorded for users who were denied access to an app when they were resetting their password. (OKTA-934302)

  • Some users received an error message when they tried to enroll in the smart card authenticator. (OKTA-964611)

  • Okta didn't redirect some users to apps when they tried to access an app. (OKTA-975872)

  • Some users who authenticated with Okta when signing in to Microsoft Entra with a smart card received an error message. (OKTA-978342)

  • Users with inactive or suspended accounts received a new account activation email when they clicked Request activation email instead of an error message. (OKTA-997612)

  • If an admin had a browser extension that used the postMessage API, they sometimes saw an error when they performed a protected action. (OKTA-1001437)

  • Some users were prompted to re-authenticate during the grace period that was configured in the authenticator enrollment policy. (OKTA-1002373)

  • When a user signed in to a custom domain and then clicked Admin in the App Switcher, they were sometimes presented with the wrong sign-in flow. (OKTA-1014174)

  • Abandoned MFA attempts were incorrectly logged in the System Log when users signed in with a Duo authenticator or IdP authenticator. (OKTA-1016718)

  • In the System Log, policy.auth_reevaluate.fail events didn't display risk unless the event was a synchronous flow and the global session policy failed without remediation. (OKTA-1017389)

Okta Integration Network

  • MIND (API Service Integration) is now available. Learn more.

  • Frame Security Platform Connector (API Service Integration) is now available. Learn more.

  • Fabrix Smart Actions (API Service Integration) is now available. Learn more

2025.9.2: Update 2 started deployment on October 6

Generally Available

Device assurance OS version update

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

  • iOS 18.7
  • macOS Sonoma 14.8
  • macOS Sequoia 15.7
  • Windows 10 (10.0.17763.7792, 10.0.19044.6332, 10.0.19045.6332)
  • Windows 11 (10.0.22621.5909, 10.0.22631.5909, 10.0.26100.6584)

Okta Provisioning agent SDK, version 3.0.3

This release contains security enhancements and support for JDK 17. See Okta Provisioning agent and SDK version history.

Certificate revocation list is deprecated

The Cache CRL for configuration option has been removed. Okta now manages the certificate revocation list cache for you.

Fixes

  • Sometimes resetting a user name for an app user failed. (OKTA-963368)

  • Some SAML apps with password synchronization enabled didn't appear on the End-User Dashboard. (OKTA-968243)

  • Group push errors sometimes appeared for apps that had provisioning disabled. (OKTA-983336)

  • Okta admins with custom admin roles couldn't confirm the assignment for an imported user. (OKTA-988692)

  • The Profile EditorUsers page didn't render correctly for some users. (OKTA-990194)

  • The System Log entry for Email Domains update operations was missing the change details for username and the domain display name. (OKTA-997246)

  • During AD and LDAP imports, group membership processing missed some updates. (OKTA-1007037)

  • Admins couldn't assign people or groups to PagerDuty when Identity Governance was enabled. (OKTA-1007080)

  • When DirSync was enabled, users located in containers had their common name (CN) changed to an invalid value. (OKTA-1007911)

  • When a user signed in to a custom domain and then clicked Admin in the App Switcher, they were sometimes presented with the wrong sign-in flow. (OKTA-1014174)

  • Temporary access code (TAC) expirations weren't recorded in the System Log. (OKTA-1015095)

  • When Governance Engine was enabled for Zoho Mail + Actions, importing users failed. (OKTA-1015810)

  • In orgs with Front-channel Single Logout enabled, some users saw an Okta-branded loading page when they signed out of their End-User Dashboard, even though the page shouldn't have been branded. (OKTA-954103)

  • The If no match is found option for non-JIT provisioning, account-linking OIDC IdPs was incorrectly labeled as Redirect to Okta sign-in page. (OKTA-961757)

  • Some users with specific characters in their name couldn't enroll in Okta Verify on any platform. (OKTA-966335)

  • Users with custom admin roles saw a Create Token button on the SecurityAPI page, even though they didn't have the required permissions. (OKTA-976743)

  • When an admin disabled provisioning for a SAML app, the provisioning settings no longer appeared on the Application > General tab. (OKTA-988899)

  • When an error was encountered during a group push event, the system incorrectly reported that the failed operation would be automatically retried. (OKTA-1017493)

  • In the Profile Editor, the checkbox for an enum property with a default value was displayed as unselected after a page refresh, even when the property's default value had been chosen. (OKTA-1020672)

  • In orgs with End User Settings version 2.0 enabled, federated users saw an error message when they tried to open the My Settings > Security Methods page. (OKTA-1022960)

  • Some users incorrectly received an "Invalid Phone Number" error when they enrolled a phone authenticator. (OKTA-1024021)

  • In the System Log, policy.auth_reevaluate.fail events didn't display risk unless the event was a synchronous flow and the global session policy failed without remediation. (OKTA-1024106)

  • Some admins saw an error message when they tried to create a custom OTP authenticator. (OKTA-1024746)

  • In some orgs with Okta Identity Governance, admins couldn't delete a policy even though there were no apps assigned to it on the Assignments tab. (OKTA-1025333)

Okta Integration Network

  • Employment hero was updated.

  • Notion was updated.

  • Briefly AI has updated the ACS, Audience URLs, and Attribute Statements.

  • Verizon MDM is now available {API Service Integration}. Learn more.