User deactivation through System for Cross-domain Identity Management (SCIM) fails to block the user profile in Auth0 because the Enterprise Connection mapping lacks the required attribute mapping. Updating the Enterprise Connection mapping to include the correct key-value pair resolves the issue. During a deactivation event, the user profile state remains active instead of changing to blocked.

• Auth0
• System for Cross-domain Identity Management (SCIM)
• Auth0 Connection Mapping
• Enterprise Connection

The user deactivation signal fails to propagate because the Enterprise Connection mapping lacks the required attribute mapping to update the Auth0 profile state.

What steps resolve the user deactivation failure?

Resolve the user deactivation failure by verifying the Enterprise Connection mapping configuration and adding the required key-value pair to the attribute mapping.

1. Verify the Enterprise Connection mapping configuration.
2. Ensure the attribute mapping contains the "auth0": "blocked" key-value pair as shown in the following code snippet.

Code Example:

{
  "scim": "active",
  "auth0": "blocked"
}

Related References

• Configure Inbound SCIM