---
title: Configuration synchronization
description: All nodes in a PingFederate clustered environment must have the same configuration settings, as set through the administrative console. You can use any of the following methods to ensure that configuration data is synchronized on all cluster nodes.
component: pingfederate
version: 13.1
page_id: pingfederate:server_clustering_guide:pf_config_synchroniz
canonical_url: https://docs.pingidentity.com/pingfederate/13.1/server_clustering_guide/pf_config_synchroniz.html
llms_txt: https://docs.pingidentity.com/pingfederate/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: July 5, 2022
---

# Configuration synchronization

All nodes in a PingFederate clustered environment must have the same configuration settings, as set through the administrative console. You can use any of the following methods to ensure that configuration data is synchronized on all cluster nodes.

* Push from the administrative console.

* Deploy configuration archive.

* Make a RESTful API call to the `/cluster` administrative API endpoint.

* Make a web service call to the `/pf-mgmt-ws/ws/ConfigReplication` Connection Management Service endpoint.

|   |                                                                                                                                                                                                             |
| - | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | Changes made directly to configuration files must be replicated manually across the cluster, as applicable. If the PingFederate servers are running, you must restart them after you replicate the changes. |