Okta Org2Org Provisioning Fails With Verification Failed Null Error
Last Updated:
Overview
When configuring Okta Org2Org provisioning using OAuth 2.0 with automatic key rotation, Okta generates an error if the application lacks either the okta.groups.manage or okta.users.manage scope. Grant both scopes in the target Okta organization to resolve this issue. During the provisioning setup, Okta displays the following error message:
Verification failed: null
The Okta Admin Console displays the verification error when attempting to save the API integration configuration.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Okta Org2Org
- OAuth 2.0 Provisioning
Cause
The OAuth 2.0 application in the target Okta organization lacks either the okta.groups.manage or okta.users.manage scope.
NOTE: If the application lacks both scopes, Okta returns a different error message: "Failed to fetch an access token."
Solution
How is the verification failed null error resolved?
Navigate to the target Okta org Admin Console where the API Services app is configured and grant the missing API scopes to the OAuth 2.0 public client app.
- Navigate to Application and Resources, and then select Applications.
- Choose the OAuth 2.0 API Services app used for Okta Org2Org provisioning, and click the Okta API Scopes tab.
- Locate and grant both the okta.groups.manage and okta.users.manage scopes.
- Access the source Okta Admin Console with the Org2Org app and retry saving the provisioning settings with Target Org Client ID.
