Okta Error Verification Failed Null Occurs During API Services App Integration
Last Updated:
Overview
An error occurs when completing the API integration for an API Services application for an Organization to Organization (Org2Org) setup. Okta generates the following error because the target application lacks the correct administrator roles and Okta API scopes:
Verification Failed: Null
Resolve this issue by assigning the appropriate administrator roles and granting the required Okta API scopes in the target organization.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Application Programming Interface (API)
- API Services Application
- Organization to Organization (Org2Org)
Cause
The target application lacks the proper permissions, including the correct administrator roles and Okta API scopes.
Solution
How does an administrator assign roles to the Service API application?
Assign the required administrator roles to the Service API application in the target organization by navigating to the administrator assignments in the Okta Admin Console.
- Log in to the Okta Admin Console of the target organization where the Service API application resides.
- Navigate to Security, and then select Administrators.
- Select the Roles tab, and then select Add Administrator or Add Assignment.
- Select App as the administrator type in the admin assignment form, and search for the name of the Service API application.
- Select the appropriate administrator role required for the provisioning or integration needs, such as Organization Administrator, Super Administrator, or a custom role with equivalent permissions.
- Select Save to apply the assignment.
An Administrator Must Grant the Okta API scopes in the Target Organization
Grant the necessary Okta API scopes to the Service API application to ensure the integration has the correct permissions.
- Navigate to Applications, and then select Applications in the target organization.
- Select the Service API application to open the application settings.
- Select the Okta API Scopes tab.
- Review the list of scopes, and select Grant for the permissions required by the integration. Common scopes for provisioning tasks include
okta.users.manage,okta.users.read,okta.groups.manage, andokta.groups.read.
How does an administrator re-verify the API integration?
Re-verify the API integration in the original organization to confirm that the connection functions correctly.
- Return to the Okta Admin Console of the original organization.
- Navigate to the Provisioning or API Integration tab of the Security Assertion Markup Language (SAML) application.
- Ensure the Base URL is formatted correctly without any trailing slashes.
- Re-enter the Client ID and Client Secret, if applicable, ensuring there are no leading or trailing spaces.
- Select Verify or Authenticate to test the connection again.
