The Okta application catalog provides several System for Cross-domain Identity Management (SCIM) Test Apps for Okta Integration Network (OIN) development. These applications allow integrators to test the Okta SCIM client against specific SCIM servers using various authorization methods.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• System for Cross-domain Identity Management (SCIM)
• Okta Integration Network (OIN)

What are the different types of SCIM Test Apps?

Okta categorizes SCIM Test Apps by SCIM version (1.1 or 2.0) and authorization method, such as Bearer token, Basic Auth, or Header Auth. Choose the application that aligns with the specific SCIM server used to test the Okta SCIM client.

SCIM Test Apps Require Specific Considerations for Development and Testing

Use SCIM Test Apps strictly for development and testing purposes. Third-party vendors must build a dedicated integration and submit it to the OIN, rather than instructing administrators to use Test App templates in production environments.

Understand the limitations of SCIM Test Apps regarding OAuth flows and update methods.

• OAuth Flow: The SCIM 2.0 Test App (OAuth Bearer Token) does not perform a standard OAuth 2.0 flow. The administrator must manually provide a bearer token and update the token when it expires. A published OIN integration automatically performs the OAuth 2.0 flow.
• Update Methods: SCIM 2.0 Test Apps use PATCH requests to update users (only for the specific operations mentioned in this Update a specific user (PATCH) document), and groups; all other operations are performed via PUT.

Related References

• Build a SCIM provisioning integration overview