In this configuration, a single instance of PingFederate serves both the identity provider (IdP) and service provider (SP) roles by sending messages to and from itself. Although this is a valid scenario for demonstration and testing, it is not applicable to a real situation.

For a more realistic test, you can deploy the configurations into instances of PingFederate running on different hosts and then make necessary configuration updates manually as shown in Advanced installation and configuration.
CAUTION: Deploying data.zip overwrites your entire PingFederate configuration. If you have configured adapters, data stores, partner connections, or any other settings, back up your configuration in step 2.
  1. Start PingFederate.
  2. Back up your current PingFederate configuration as shown in Configuration archive in the PingFederate documentation.
  3. From the Java Integration Kit .zip archive, copy the sample/data.zip archive to <pf_install>/pingfederate/server/default/data/drop-in-deployer/.
    PingFederate adopts the new configuration and renames the data.zip file with a time stamp.