Okta Privileged Access release notes

Learn about new features, enhancement, and fixes in the latest version.

See the Okta Support website for the list of supported operating systems with End of Life (EOL) dates.

Version: 1.97.1

Device tools

Deployment date: September 18, 2025

Release summary

Client

  • The sft list-accounts command, which was previously deprecated, has now been officially removed. Use the sft list-teams command instead.

  • The SFT client now adds the server name to the username when connecting through RDP using the Windows and FreeRDP clients.
Gateway

  • A bug in Windows 10 and Windows 11 was sending the wrong channel ID to Windows Server 2025. This prevented RDP through the gateway from working.

  • When connecting from a Windows 11, version 24H2 client to a Windows Server 2016, the connection may fail if a gateway is used. If a gateway is not used, the RDP session may disconnect and reconnect several times before stabilizing.

Client

Server Agent

  • Digital signature verification has been added for all DLLs loaded from outside the trusted system paths.

Version: 2025.9.1

Platform

Deployment date: September 19, 2025

Release summary

The following releases are now in Preview:

Auto-generate passwords for SaaS apps is EA

Okta Privileged Access users can now use the password generator feature to update the password for their unmanaged SaaS apps. See Okta Privileged Access user guide.

The following releases are now in Production:

Okta-managed Active Directory accounts is EA

You can now set up Active Directory (AD) account rules to import users managed by Okta. Enabling an AD account allows active users to sign in to Okta and access their SSO apps through the End-User Dashboard. Admins and users can rotate passwords via Okta Privileged Access, with synchronization occurring between the AD server and Okta. You can also filter account names or Okta group memberships when configuring AD account rules with user management capabilities enabled. See Active Directory account rules.