The legacy Persona identity verification (IDV) provider for Okta’s Account Management Policy uses a Persona API key. The new Persona IDV integration uses OpenID Connect (OIDC), Pushed Authorization Requests (PAR), and Verified Claims. Okta’s legacy API-key-based Persona IDV integration reaches end of life on September 15, 2027, so organizations using it need to migrate before then.
Who needs to migrate
You need to migrate if your organization uses the legacy Okta IDV provider, the API-key-based Persona provider, for Okta’s Account Management Policy.
This migration does not apply if:
- You are setting up IDV for the first time. Use Configure Persona for the Okta Account Management Policy instead.
- Your provider is already Custom ID verification with OIDC and PAR.
- You use Okta SSO to sign in to the Persona Dashboard.
- You use Persona as an authentication method in Okta application sign-on policies.
Migrate with the wizard
Start the migration in the Okta legacy IDV migration wizard in the Persona Dashboard. The wizard walks you through the whole migration. If the wizard isn’t available in your organization, contact your Persona account team for migration assistance.
You will need Okta administrator access and Persona Dashboard access, so coordinate with your Okta and Persona administrators if these permissions belong to different people. Your existing provider and policy rules stay in place until you cut over to the new integration.
Plans Explained
Okta Integration by plan
| Startup Program | Essential Plan | Growth Plan | Enterprise Plan | |
|---|---|---|---|---|
| Okta Integration | Not Available | Not Available | Limited | Available |