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. The legacy Okta Persona IDV integration that uses an API key reaches end of life on September 15, 2027. Organizations that use it must migrate before that date.
Who needs to migrate
You must migrate if your organization uses the legacy Okta IDV provider for the Okta Account Management Policy. This is the Persona provider that uses an API key.
This migration does not apply if:
- You configure 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 shows you all of the migration steps. If the wizard is not available in your organization, contact your Persona account team for help with the migration.
You need Okta administrator access and Persona Dashboard access. If different people have these permissions, work with your Okta and Persona administrators. Your current provider and policy rules stay in place until you change 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 |