Ping Identity Platform

Prepare the servers

This is not a comprehensive platform implementation guide. These sample setup instructions show a minimal integration of platform components to get you started.

The Ping Identity Platform offers maximum extensibility and flexibility in self-managed deployments. The platform includes many features and options these sample setup instructions do not cover. If you don’t need maximum extensibility and flexibility, there are simpler alternatives:

For help with your deployment and to validate your plans before deploying in production, contact Ping Identity.

Downloads

The sample deployments use software from the Download Center and other locations.

Download the required files for your sample deployment:

Component Downloads

PingAM

AM-8.0.1.zip

Amster-8.0.1.zip

apache-tomcat-10.1.36.zip1

PingDS

DS-8.0.0.zip

PingIDM

IDM-8.0.0.zip

mysql-8.0.29-macos12-x86_64.tar.gz2

mysql-connector-java-8.0.29.zip2

PingGateway

PingGateway-2025.3.0.zip

Platform UI3

PlatformUI-8.*.zip

1 Download this from the Apache site; Ping Identity doesn’t ship Apache software.

2 Separate identity stores deployment only. Download these from the MySQL site; Ping Identity doesn’t ship MySQL software.

3 (Optional) The alternative is to pull the Platform UI Docker images.

Basic requirements

These basic evaluation requirements concern the sample deployments.

Before deploying the platform in production, make sure the deployment meets all the requirements for each server component product. Find more information in the release notes for each product.

Memory and disk space

These are basic sizing requirements for each sample deployment:

  • Reserve 1 GB RAM for each server product you install.

  • Reserve at least 10 GB disk space for the files.

  • For PingDS, reserve 5% + 1 GB of the filesystem size as free disk space.

Production deployments may have very different requirements.

Operating systems

Common supported operating systems for the server component products include:

  • Microsoft Windows Server

  • Red Hat Enterprise Linux and Rocky Linux

  • Ubuntu Linux

For details, read the release notes for each product.

Although it is not a supported operating system for the platform, you can try the sample deployments on Apple macOS.

Java

Supported Java versions for the sample deployments include:

  • Java 21

Before installing the servers, set the JAVA_HOME environment variable.

Keep your Java installation up-to-date with the latest security fixes. Some security features may require later updates.

For details, read the release notes for each product.

Hosts and ports

The sample deployments use these hostnames and port numbers:

Component Hostname Port numbers

PingAM

am.example.com

HTTP: 8081

PingDS

directory.example.com

Admin: 4444

LDAP: 1389

LDAPS: 1636

PingIDM

openidm.example.com

HTTP: 8080

HTTPS: 8443

PingGateway

platform.example.com

HTTP: 9080

HTTPS: 9443

Platform Admin UI

admin.example.com

HTTP: 8082

Platform End User UI

enduser.example.com

HTTP: 8888

Platform Login UI

login.example.com

HTTP: 8083

Sample deployment on a single computer

The sample deployments assume all servers are deployed on their own hosts.

To try a sample deployment on a single computer, the recommended alternative is to use the ForgeOps Cloud Developer’s Kit (CDK) on Minikube.

If you nevertheless choose to demonstrate these sample deployments on your computer, add aliases for the fully qualified domain names used for the servers and platform UIs to your /etc/hosts file:

127.0.0.1    admin.example.com
127.0.0.1    am.example.com
127.0.0.1    directory.example.com
127.0.0.1    enduser.example.com
127.0.0.1    login.example.com
127.0.0.1    openidm.example.com
127.0.0.1    platform.example.com

Next step