---
title: Synchronization server considerations
description: Changes involving composed attributes should be synchronized from a PingDirectory server instance to another endpoint type without issues. Changes that create or update composed attributes should be written to the LDAP changelog, just like changes to regular attributes.
component: pingdirectory
version: 11.0
page_id: pingdirectory:pingdirectory_server_administration_guide:pd_ds_sync_server_considerations
canonical_url: https://docs.pingidentity.com/pingdirectory/11.0/pingdirectory_server_administration_guide/pd_ds_sync_server_considerations.html
revdate: September 13, 2023
---

# Synchronization server considerations

Changes involving composed attributes should be synchronized from a PingDirectory server instance to another endpoint type without issues. Changes that create or update composed attributes should be written to the LDAP changelog, just like changes to regular attributes.

Synchronization to PingDirectory server configured with one or more composed attribute plugin instances might be more problematic. It might not be possible to synchronize a composed attribute type if the plugin that generates values for that attribute is configured to prohibit external clients from altering values of that attribute.

If PingDirectory server is used as a sync destination in an environment in which some attribute values might need to be composed, then you should compose those values in the Synchronization Server using a constructed attribute mapping *(tooltip: \<div class="paragraph">
\<p>Matching corresponding attributes between an IdP and an SP to identify federated users or add supplemental user information.\</p>
\</div>)* rather than attempt to generate them in the PingDirectory server with the composed attribute plugin.