IPS Sync Troubleshooting
This section describes how to diagnose and resolve synchronization issues in the Identity Provisioning Service (IPS). It covers logging configuration, common diagnostic checks, and practical troubleshooting steps.
When investigating IPS synchronization issues, enabling detailed logging is the first and most critical step. Enhanced logs help identify failed or skipped entities and provide visibility into the data payload exchanged between the source and target systems.
ips.trace.failed.entity.content=true ips.trace.skipped.entity=true ips.trace.skipped.entity.content=true ips.delete.threshold.groups =1 ips.delete.threshold.users = 1
Follow the steps below to systematically identify and resolve IPS synchronization issues:
-
Review Error Logs.
-
Examine IPS logs for failed or skipped entities.
-
Pay close attention to error messages, entity identifiers, and timestamps.
-
Use the detailed entity content logs to understand exactly what data caused the failure.
-
-
Determine the Failing Side.
-
Identify whether the issue originates from the source (for example, incorrect data format or missing attributes) or the target (for example, API validation errors or authorization failures).
-
-
Validate the Payload.
-
Compare the logged payload against the target system’s API documentation.
-
Check attribute names, data types, mandatory fields, and value constraints.
-
Ensure that any custom mappings or transformations are correctly applied.
-
-
Re-test After Adjustments.
-
After making corrections to mappings, transformations, or configuration, rerun the synchronization.
-
Monitor the logs again to confirm that entities are processed successfully.
-