System requirements
PingFederate has the following recommended system versions and requirements.
Operating systems and virtualization
PingFederate is tested with default configurations of operating-system components. If your organization customizes implementations or installs third-party plug-ins, deployment efforts might affect the PingFederate server. |
Component | Supported versions | ||
---|---|---|---|
Operating systems |
|
||
Docker support |
|
||
Virtualization |
Although Ping Identity does not qualify or recommend any specific virtual-machine (VM) or container products other than those already specified, PingFederate has run well on several, including Hyper-V, VMWare, and Xen.
|
Java environment
-
Amazon Corretto 8, 11, and 17
-
OpenJDK 11 and 17
-
Oracle Java SE Development Kit 11 LTS and 17 LTS
-
Oracle Java SE Runtime Environment (Server JRE) 8
Ping Identity Java Support Policy applies. Learn more in Java Support Policy in the Ping Identity Knowledge Base. |
PingFederate does not support any JDK 11 version prior to 11.0.4 due to an error covered in the Oracle Java Bug Database. |
Browsers
Server | Supported browsers |
---|---|
Runtime server |
|
Administrative server |
|
Datastore integration
Functionality | Supported versions |
---|---|
User-attribute lookup |
|
SaaS or SCIM outbound provisioning |
|
SCIM inbound provisioning |
|
Just-in-time (JIT) inbound provisioning |
|
Account linking |
|
OAuth client configuration and persistent grants |
|
Registration and profile management of local identities |
|
Persistent authentication sessions |
|
If you have Microsoft Active Directory environments on the 2012 R2 functional level, you should upgrade to a later version. Learn more, including the end of support for the 2012 R2 functional level in July 2023, in Upgrade considerations introduced in PingFederate 10.x. |
PingFederate was tested with vendor-specific Java database connectivity (JDBC) 4.2 drivers. Learn more in Compatible database drivers. |
Hardware security modules (optional)
When integrating with an AWS CloudHSM hardware security module (HSM), Thales Luna HSM, or Entrust nShield Connect HSM, you must deploy with an Oracle Server Java Runtime Environment (JRE), OpenJDK, or Amazon Corretto distribution of Java 8 or 11. |
Hardware security module | Supported versions |
---|---|
AWS CloudHSM |
|
Entrust nShield Connect HSMs |
|
Thales Luna Cloud HSM Services and Luna Network HSM |
|
Minimum hardware requirements
-
Multi-core Intel Xeon processor or higher
We recommend a minimum of four processing cores distributed across any number of CPUs.
-
4 GB of RAM
Step 1.5 GB available to PingFederate
-
1 GB of available hard drive space
Although it’s possible to run PingFederate on less powerful hardware, the guidelines provided accommodate disk space for default logging, auditing profiles, and CPU resources for a moderate level of concurrent request processing. |