This second suite of Runscope tests checks that your SCIM app can handle actual requests to Create, Read, Update and Delete (CRUD) user profile information.
Note: Okta does not delete user profiles, but instead marks them as
active=falseto deactivate them.
If you are not familiar with Runscope, follow the detailed instructions in the test your SCIM API topic to get started.
This suite runs the following tests:
firstNameattribute in Okta.
To configure and run the SCIM CRUD tests:
Download the Okta SCIM CRUD test file.
In Runscope, click Import Test.
Select Runscope API Tests as the import format.
Click Choose File and select the Okta SCIM 2.0 CRUD JSON test file.
Click Import API Test.
In this new test bucket, click Editor from the left hand navigation menu.
Click Test Settings and then click Initial Variables.
Add the following variables with values that match your SCIM app:
oktaAppId- the unique identifier randomly assigned to your Okta app. You can see this value in the App Embed Link panel under the General tab for your Okta app.
oktaOrgUrl- the base URL for your Okta org. Include the
oktaToken- the security token used to connect to your Okta app API. You can generate a token for your app inside your Okta org:
SCIMUrl- the Base URL of the SCIM implementation on your server. For example:
SCIMAuth- the Basic or OAuth authorization token used to access your SCIM API.
The final Runscope values should look similar to the following:
Click Test Settings and then click Initial Script.
Copy the contents of the Okta CRUD Initial Script text file and paste into this Runscope console.
Click Save & Run.
On the left side of your screen, the test appears in the Recent Test Runs section.
After the tests complete successfully, you can move on to creating the configuration guide for your customers to use your app once it is available on the OIN.
For comparison and reference, here is an example of a successful Runscope test run for the SCIM 2.0 CRUD test suite.Next: