When submitting a System for Cross-domain Identity Management (SCIM) application to the Okta Integration Network (OIN), ISV partners must run a Runscope test suite to validate their SCIM implementation. During test execution, the following errors may be encountered"

Unable to execute empty request
Request failed to set 'body' — Variable 'okta_user_firstname' was not defined

Or the following API validation error is returned:

"errorCode": "E0000001",

"errorSummary": "Api validation failed: assignment"

{
  "errorCode": "E0000001",
  "errorSummary": "Api validation failed: assignment",
  "errorCauses": [
    { "errorSummary": "Property 'emailType' not found" },
    { "errorSummary": "Property 'familyName' not found" },
    { "errorSummary": "Property 'givenName' not found" }
  ]
}

• Okta Integration Network (OIN) App Submission Process
• ISVs Submitting to OIN
• Runscope System for Cross-domain Identity Management (SCIM) Test Suite
• Okta Identity Engine (OIE)

The Runscope test suite requires an active API connection between the Okta org and the SCIM application to initialize test variables and execute requests. When Configure API Integration has not been enabled under Provisioning > Integration, the SCIM Base URL and API Token are not configured, leaving Runscope without a connection to the SCIM server. This causes all tests to fail with variable errors, empty request errors, or API validation failures.

Before running the Runscope test suite, Enable API Integration in the Okta Admin Console. This step is a prerequisite as outlined in the following Okta documentation: Submit an integration with the OIN Wizard.

1. In the Okta Admin Console, navigate to Applications > Applications.
2. Select the SCIM app integration being submitted to OIN.
3. Click the Provisioning tab.
4. Click Integration in the left sidebar.
5. Click Configure API Integration.
6. Select the Enable API Integration checkbox.
7. Enter the SCIM 2.0 Base URL and API Token for the SCIM server.
8. Click Test API Credentials to verify the connection.
9. Click Save.
10. Return to the Runscope test suite and re-run the tests.