Uploading configuration archives is an alternate method of copying configurations to clustered PingFederate servers.
After you configure or reconfigure the console, you can also update cluster nodes by downloading a configuration archive from the <pf_install>/pingfederate/server/default/data/drop-in-deployer directory on each cluster node or provisioning-failover server.window and then deploying it either manually or using a scripted process to the
If you use the drop-in deployment process:
- PingFederate will not let you import the configuration archive of an older or newer version, and to ensure successful importation of the configuration archive file with this process, you must rename the file data.zip.
- On startup, the heartbeat endpoint will not return
200until the archive import completes. If you have configured a health check or probe that can trigger a restart of the server, crash loop behavior can result. Review the configuration of these checks to ensure time thresholds are set appropriately.
A configuration archive contains the same information sent during the configuration push from the administrative console described in Console configuration push. However, configuration-archive deployment also provides for scheduling and scripting cluster synchronization.
Runtime state-management services
If you have configured one of the following runtime state-management services on the engine nodes, you must manually migrate the configuration files to the engine nodes. The configuration files are located at <pf_install>/pingfederate/server/default/conf
|RPC-based service implementation
|Account Locking Service
|Artifact-Message Persistence and Retrieval Service
|Assertion Replay Prevention Service
|IdP Session Registry Service
|Inter-Request State-Management (IRSM) Service
|Back-Channel Session Revocation Service
|SP Session Registry Service