This article describes errors encountered during a System Cross-domain Identity Management (SCIM) integration when provisioning events are sent. These errors persist even after the integration is verified, and all provisioning options are enabled in the application.

• SCIM 2.0
• Lifecycle Management

A discrepancy exists between the expected schema and the schema sent by the identity provider. Differences in attribute contents, the attributes themselves, or formatting issues within SCIM calls lead to these errors.

The following resources provide transparency on the schema and allow for testing:

• SCIM 2.0 Protocol Reference

• SCIM Playground Playbook

Due to data security standards regarding Personally Identifiable Information (PII), the body of SCIM calls sent to third-party servers is not logged.

To access the information within the SCIM calls, follow these steps:

1. Check the SCIM provider logs for the specific call body.

2. Set up a test SCIM server through SCIM Playground or another provider.

3. Connect an Okta SCIM compatible SAML application to the test server to view the SCIM calls and identify formatting or content errors.

4. Coordinate with the SCIM provider's support resources to ensure compatibility with internal systems.