For optimal performance, the server requires Java for 64-bit architectures. To view the minimum required Java version, contact your authorized support provider for the latest supported software versions.


Implement a Network Time Protocol (NTP) system so that multi-server environments are synchronized and timestamps are accurate.

The following system requirements are qualified and certified to be compatible with the PingDirectory server.

Differences in operating system versions, service packs, and other platform variations are supported until the platform or other required software are suspected of causing issues.

CPU and memory
When sizing an instance of the PingDirectory server, provide at least the following minimum specs:
  • 2 processor cores
  • 4 GB of RAM

For more information about memory allocation, see Memory allocation and database cache or Finding the optimal heap size (requires authentication).

Running PingDirectory on Amazon Web Services (AWS)
To take advantage of snapshots for backing up any important files, install the PingDirectory server on an Elastic Block Store (EBS) file system. You should also move any databases, logs, and other files to a high-performance file system that is separate from the rest of the server image, and create an S3 bucket for storing backups, schema, and other artifacts.

The following guidelines and considerations can help you avoid environmental constraint issues:

  • PingDirectory does not support the Elastic File System (EFS) for database persistence.
  • For the lowest cost, use t3.medium or t3a.medium and up.
  • For the best performance, use m5dn, c5dn, or r5dn instance types (size xlarge and up) and the local SSD for PingDirectory database persistence.
  • The A1 and M6g instance types, Ampere and Graviton, are not qualified by Ping Identity at this time.
  • Using network load balancers (NLBs) can lead to severed connections, which could cause issues that are difficult to diagnose.
The PingDirectory, PingDirectoryProxy, and PingDataSync servers support the following operating systems for installation and deployment:
  • Amazon Linux 2022
  • Canonical Ubuntu 18.04 LTS and 20.04 LTS
  • CentOS 7.7 and 8.1
  • Microsoft Windows Server 2016, 2019, and 2022
  • Oracle Linux 7.9, 8.6, 8.8, and 9.2
  • Red Hat Enterprise Linux ES 7.9, 8.7, 8.8, 8.9, 9.0, 9.1, and 9.2
  • SUSE Enterprise Linux 12 SP5, 15 SP3, and 15 SP4
To deploy the PingDirectory server using Docker, you must have a supported version of Docker. The following versions of Docker are supported:
  • Docker 20.10.9

For more information, see the pingidentity/pingdirectory Docker image and the Ping Identity DevOps documentation.


Only the PingDirectory server software is licensed under Ping Identity’s end user license agreement, and any other software components contained within the image are licensed solely under the terms of the applicable open source or third-party license.

Ping Identity accepts no responsibility for the performance of any specific virtualization software and in no way guarantees the performance or interoperability of any virtualization software with its products.

Java Runtime Environment
You must have one of the following versions of the Java Development Kit installed prior to installing the server:
  • Oracle JDK 11 LTS 64-bit
  • Oracle Java 17
  • OpenJDK 11 and 17
  • Corretto 11

Because of the number of supported JDK variants, we do not explicitly list all of them here. The criteria for supported JDKs are:

  • They must be built from the OpenJDK codebase.
  • They must use the HotSpot JIT compiler. They cannot use OpenJ9 or other JIT implementations.
The following browsers are supported by the PingDirectory server administrative console:
  • Chrome
  • Firefox
  • Edge