To handle data synchronization through a proxy server, PingData servers have a cn=changelog state management system that supports a token-based API.

In a standard, non-proxied configuration, PingDataSync Server polls the source server for changes, determines if a change is necessary, and fetches the full entry from the source. Then, it finds the corresponding entry in the destination endpoint using correlation rules and applies the minimal set of changes. The server fetches and compares the full entries to make sure it does not synchronize any stale data from the change log.

In a proxied environment, PingDataSync Server passes the request through a proxy server to the backend set of directory servers. PingDataSync Server uses the highest priority proxy server designated in its endpoint server configuration and can use others in the event of a failover.

The following figure illustrates a deployment with two endpoints consisting of a proxy server deployment in front of the backend set of directory servers.

Synchronize with a SCIM sync destination