Okta Identity Engine Production release notes

Subscribe to RSS

Version 2026.46.0. Deployed on November 12, 2026.

Generally Available Features

Email auto-enroll note for authenticator sets

Authenticator enrollment policies that use authenticator sets now include a note that explains how automatic enrollment works to help you understand when email is enrolled automatically.

User email addresses in the Cross App Access Token Analytics report

The Cross App Access Token Analytics report now includes user email addresses. See the Cross App Access Token Analytics report.

Enhanced breached credentials protection for OWI

This feature provides a premium breached credentials detection feed for Okta Workforce Identity customers with Identity Threat Protection that identifies more compromised credentials sooner. See Breached credentials protection.

Desktop MFA Factor Discovery for Windows

Desktop MFA for Windows now shows users only the MFA factors they've enrolled, instead of a fixed list of all available factors. New users without an enrolled factor can sign in during their grace period to set up MFA, while existing users signing in on a new device must verify with an existing factor. See Enable Desktop MFA Factor Discovery.

Platform SSO password integration with Device-Bound SSO

The Platform SSO password authentication method now integrates with Device-Bound SSO. When a user signs in at the macOS sign-in window, Okta verifies the password factor and creates a device-bound session. Users can then access Okta-protected apps in their browser without additional password prompts. See Platform SSO for macOS and Configure device configuration profiles for PSSO using a generic MDM.

Secure Enclave key support for Platform SSO

Platform SSO now supports a Secure Enclave key-based authentication method that integrates with Device-Bound SSO. When a user authenticates at the macOS sign-in window with their password, the authentication unlocks a hardware-bound cryptographic key stored in the Secure Enclave. Okta uses the key to create a device-bound session that satisfies any authentication policy that requires Okta FastPass with user verification, without repeated MFA prompts. See Platform SSO for macOS and Configure device configuration profiles for Secure Enclave using a generic MDM.

Device-Bound Single Sign-On

Device-Bound Single Sign-On initiates a hardware-protected session for seamless access to apps after users sign in to Okta-joined macOS and Windows devices. This feature provides session replay protection and a streamlined authentication experience. See Device-Bound Single Sign-On.

Increased Access Request task assignee limit

The maximum number of assigned users per task or question has been increased to 50 (previously 25).

Okta On-Prem MFA agent version 1.8.9

This version includes security enhancements.

Okta Active Directory agent, version 3.24.0

This release includes the following changes: Performance improvements and bug fixes. See Okta Active Directory agent version history.

Workday incremental imports and import scheduling

Incremental imports and import scheduling are now available for Workday. Admins can independently schedule full and incremental imports to keep Workday worker data current with a cadence that fits their org. See Workday incremental imports.

This feature is following a slow rollout process, with deployment to all orgs completing by early December.

Okta Provisioning Agent, version 3.3.4

Okta Provisioning Agent 3.3.4 is now available. This release includes the following changes: Updated the bundled Amazon Corretto JRE to 17.0.21.1.2, vulnerability fixes, and security fixes. See Okta Provisioning Agent and SDK version history.

Generally Available Enhancements

Passkey (FIDO2 WebAuthn) support for user identification policies

You can now manage rules in the user identification policy to control whether the Sign in with a passkey button appears on an app-by-app basis, instead of relying on a single org-wide setting. This makes it easier to manage pilot groups during passkey rollouts and to tailor the sign-in experience for individual apps. See Add a rule to a user identification policy.

AI agent profile attributes as custom claims

You can now include AI agent profile attributes as custom claims in access tokens. This provides downstream resources with AI agent metadata for granular authorization checks and enhanced security logging.

Early Access Features

Attack protection policy

Bot protection currently uses one detection threshold and one action for every protected flow. Admins have to choose between letting more bots through on sign-up or adding friction to every sign-in. With the attack protection policy, admins create a rule for each sign-in, sign-up, and password reset flow, with its own bot likeliness threshold and action. This lets admins enforce Okta Challenge where bot traffic costs the most and monitor the rest. When you enable the feature, your existing bot protection settings migrate to the policy automatically. See Attack protection+.+

Early Access Enhancements

Automated Admin Console banner for paused imports

When an import safeguard pauses an import and triggers a system.import.roadblock System Log event, Okta now displays a notification banner. The banner alerts admins and links to the Import Monitoring page to review, resume, or cancel affected imports.

Fixes

  • After admins uploaded a signature certificate for a new custom SAML 2.0 app, the Signature Certificate field didn't appear on the General tab. (OKTA-1240578)

  • In some orgs, users on iOS devices got stuck in a loop when they tried to enroll in Okta Verify on a second device. (OKTA-1249225)

  • The Role column on the API Tokens page displayed "User" instead of the admin role for tokens created by custom admins. (OKTA-1255371)

  • In orgs that use the Okta Account Management Policy, legacy authenticators selected in a policy were still available for enrollment on the End-User Dashboard settings page, even though they were disabled in all policies. (OKTA-1271381)

  • For orgs with authenticator enrollment policies that use authenticator sets, the email authenticator wasn't automatically enrolled when the set required all of its authenticators. (OKTA-1289944)

  • In orgs with the Authenticator enrollment sets Early Access feature enabled, admins saw an error message when they edited a legacy authenticator enrollment policy. (OKTA-1304440)

  • Some MCP servers returned unvalidated token and registration endpoint URLs.  (OKTA-1317736)

Okta Integration Network

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

  • Barndoor AI now supports XAA.

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

  • Ferentin (XAA) is now available. Learn more.

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

  • NanoCo (XAA) is now available.

  • Opal Security (XAA) is now available. Learn more.

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

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

  • Suppleo now supports Universal Logout.

  • Wiz (API Service) was updated. Learn more.