Ping Advanced Identity Software

Prepare the servers

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

Ping Advanced Identity Software offers maximum extensibility and flexibility in self-managed deployments. It includes many features and options the sample setup instructions don’t cover. If you don’t need maximum extensibility and flexibility, there are simpler alternatives:

  • To consume Ping Advanced Identity Software as a service, use PingOne or Advanced Identity Cloud instead.

  • To deploy Ping Advanced Identity Software in Kubernetes, start with the ForgeOps reference implementation.

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 Ping Identity Product Downloads and other locations.

Download the required files for your sample deployment:

Component Downloads

PingAM

AM-8.1.1.zip

Amster-8.1.1.zip

A supported Apache Tomcat ZIP distribution as documented in the PingAM release notes1

PingDS

DS-8.1.1.zip

PingIDM

IDM-8.1.1.zip

A supported MySQL server as documented in the PingIDM release notes2

A supported MySQL connector as documented in the PingIDM release notes2

PingGateway

PingGateway-2026.6.zip

Platform UI3

PlatformUI-8.1.1.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 file system 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

Learn more in 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 25

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.

Learn more in 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

Advanced Identity Software Admin UI

admin.example.com

HTTP: 8082

Advanced Identity Software End User UI

enduser.example.com

HTTP: 8888

Advanced Identity Software 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 an out-of-the-box ForgeOps deployment.

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