This article outlines the steps to obtain a test SCIM server and add it to an Okta org.

NOTE: Only use test data with the SCIM playground. Do not export any sensitive information.

• API Access Management
• SCIM
• Integration

Use case: This guide provides a quick and easy way for a developer to create and test a SCIM integration.

1. Navigate to https://scim.dev/ and create a unique API key for the test:
   1. Click Get an API key.
   2. Review and accept the terms and conditions.
   3. Click on Access My Playground.
      • The API key is valid for 24 hours by default, but this time period can be set to a shorter or longer value before generating it.
   4. The API key from the Show API Key section must be stored in Notepad or an alternative external location for future reference.

2. Click on Playground in the top-right corner, then Data Generator in the left-hand pane to access options to generate mock data for the test SCIM server:
   1. Click on the Generate Users button
   2. Click on the checkbox beside Create activated users, then click the Generate Users button
   3. Click on the Generate Groups button
   4. Click on the Assign Users to Groups button

3. In the Okta Admin Dashboard, create a SCIM application
   1. Navigate to Applications > Applications, then click on Create App Integration.
   2. Choose SAML 2.0, then click Next.
   3. Enter a relevant value for App Name, then press Next.
   4. In SAML Settings, use https://scim.dev/ as the Single sign-on URL and Audience URI, then press Next.

1. 5. For the App type, choose This is an internal app that we have created

1. 6. Click Finish to complete the application's creation.
      Now our application is created!

4. Click on the General tab, then Edit within App Settings.
   For Provisioning, choose SCIM and Save.

5. A Provisioning tab should now be available. Navigate to this Provisioning tab, then click Edit and configure the integration with the following details:
   1. SCIM connector base URL: https://api.scim.dev/scim/v2.
   2. Unique identifier field for users: userName.
   3. Check all the boxes beside Supported provisioning actions.
   4. Authentication Mode: HTTP Header.
   5. HTTP Header > Authorization: Paste the API Key obtained from the SCIM playground.
   6. Press Save.
6. The page should be updated with new options. In the Provisioning to App (To App settings), click Edit, enable all options, then click Save.

The application is now ready for testing! Users can be assigned to the SCIM server, imported from the SCIM server, or groups can be pushed.

A starting point can be reproducing the calls from this documentation: Okta and SCIM Version 2.0.

Additionally, interactions with Okta can be seen in the SCIM Playground by navigating to Logs > HTTP Logs: