After configuring outbound provisioning, you can set up one or more PingFederate failover servers specifically for provisioning backup.
Provisioning runtime processing and failover is independent of single sign-on (SSO) or single logout (SLO) runtime processing and server clustering. However, if you are already deploying, or have deployed, a cluster for federation-protocol runtime processing, you can use a subset of those servers for provisioning failover. Alternatively, you can mix the configuration or set up provisioning-failover servers independently.
Each server in the failover network must be configured to use the same relational database.
Use the built-in HSQLDB only for trial or training environments. For testing and production environments, always use a secured external storage solution for proper functioning in a clustered environment.
Testing involving HSQLDB is not a valid test. In both testing and production, it might cause various problems due to its limitations and HSQLDB involved cases are not supported by PingIdentity.
- Select two or more runtime instances of PingFederate to configure for provisioning failover.
For each server instance, edit provisioning properties in the
file as follows:
Property Description pf.provisioner.mode The status of outbound provisioning. Allowed values are:
- Outbound provisioning is disabled.
- Provisioning is enabled, without failover.
- Provisioning is enabled, with failover.
STANDALONEcannot be used for failover configuration. This property must be set to
FAILOVERon the primary and secondary servers.
provisioner.node.id The unique index number of the provisioning server.
Each server must have a unique index number, which is used to prioritize which server is currently active and which is next in line in case of a failure. Values are any number.Important:
The primary active primary server should have an index number of 1. The lowest value in the environment becomes the primary.
These node IDs are not required to start at 1, but it is recommended that they start at 1. The node IDs for each node must increase sequentially. The number must not exceed the maximum integer value supported by Java, which is 2147483647. Initial start-up performance degradation may result if the node ID does not start at 1.
provisioner.failover. grace.period The time interval (in seconds) between the first indication that a node is dead and failover to the next server in line. The time period should be greater than the Synchronization Frequency set in the tab on the administrative console.
The default value is
600, which is 10 minutes.Important:
You must seperately configure the failover properties in the run.properties file on each provisioning server, because the run.properties file is not copied among the provisioning servers automatically or as part of the Replicate Configuration process.
- Start or restart all of the PingFederate servers.
- If you have not already done so, set up an external database to facilitate provisioning and then update the Internal Provisioning Data Store setting on the tab. See Configuring outbound provisioning settings for more information.
- After configuration, if the provisioning servers belong to the same PingFederate clustered environment, go to the Cluster Managementwindow, replicate the new Internal Provisioning Data Store setting to all nodes. If the provisioning servers are individual PingFederate servers, for each provisioning server, create a datastore connection to the same external database and update the Internal Provisioning Data Store setting manually. . In the