Okta Privileged Access Platform release notes

Generally Available features

Workload identity for automation is now available in Okta Privileged Access

Workload identity for automation eliminates the need for hardcoded API keys or service account secrets. It does this by using a workload's native platform identity and a runtime OIDC token to securely authenticate automated workloads. This works with platforms like GitHub Actions, GitLab CI, Google Cloud Platform, and Azure Managed Identity. See Workloads.

Active Directory accounts available during rotation failures

If an Active Directory account password fails to rotate after an initial successful onboarding, the account status now remains Available. This enhancement ensures continued access to the account using the existing password while rotation issues are resolved.

Improved Active Directory discovery pipeline

The Okta Privileged Access discovery pipeline for Active Directory accounts now resumes from the last successful stage if a timeout or error occurs. This improvement reduces processing time by preventing the need to restart the entire sequence.

Expanded Active Directory account management

Okta Privileged Access now uses Active Directory (AD) as the source of truth for discovered AD accounts when the Keep as existing Okta user setting is disabled. This enhancement enables the discovery of AD accounts even if they aren't synced with Universal Directory, ensuring more comprehensive account management and faster discovery. Initial rotation for a large batch of new accounts may be a bit slower if the AD accounts aren't in Universal Directory.