Okta User Reactivation Fails to Sync Status Update With Downstream SCIM Server

When Okta reactivates a previously provisioned user, the downstream System for Cross-domain Identity Management (SCIM) server fails to receive the correct active status. This occurs when the SCIM server returns inconsistent active statuses during the reactivation GET requests. Ensuring the SCIM server consistently returns the correct active status for both List Users and Single User requests resolves the issue. 

• Okta Identity Engine (OIE)
• Okta Classic Engine
• System for Cross-domain Identity Management (SCIM) Provisioning

When Okta reactivates a user, Okta makes two GET calls

• List Users Endpoint with a filter (/v1/scim/Users?filter=userName...)
• Get User Endpoint (/v1/scim/Users/<uuid>)

If the first call returns active=true and the second call returns active=false, Okta sends active=false to the SCIM server during the status update.

How is the downstream SCIM status update issue resolved?

Update the downstream SCIM server configuration to return consistent user records for both List Users and Get User endpoints.