Requirements
Files to download
PingAM software is available at https://backstage.forgerock.com.
The following table describes the files available for download.
File | Description |
---|---|
|
Cross-platform distribution including all software components. Find a list of the files in the |
|
Deployable web application archive file. |
|
The .zip file that contains tools to manage AM from the command line. |
|
The .zip file that contains tools to configure AM from the command line. |
Files for previous versions
File | AM 7.0 | AM 7.1 | AM 7.2 | AM 7.3 | AM 7.4 | AM 7.5 |
---|---|---|---|---|---|---|
AM |
AM-7.0.2.zip |
AM-7.1.4.zip |
AM-7.2.2.zip |
AM-7.3.2.zip |
AM-7.4.2.zip |
AM-7.5.1.zip |
AM |
AM-7.0.2.war |
AM-7.1.4.war |
AM-7.2.2.war |
AM-7.3.2.war |
AM-7.4.2.war |
AM-7.5.1.war |
AM SSO Admin Tools |
SSOAdminTools-5.1.3.11.zip |
SSOAdminTools-5.1.3.19.zip |
SSOAdminTools-5.1.3.27.zip |
SSOAdminTools-5.1.3.28.zip |
SSOAdminTools-5.1.3.29.zip |
SSOAdminTools-5.1.3.28.zip |
AM SSO Configurator Tools |
SSOConfiguratorTools-5.1.3.11.zip |
SSOConfiguratorTools-5.1.3.19.zip |
SSOConfiguratorTools-5.1.3.27.zip |
SSOConfiguratorTools-5.1.3.28.zip |
SSOConfiguratorTools-5.1.3.29.zip |
SSOConfiguratorTools-5.1.3.28.zip |
Operating systems
PingAM software is supported on the following operating systems:
Operating system | AM 7.0 | AM 7.1 | AM 7.2 | AM 7.3 | AM 7.4 | AM 7.5 | AM 8.0 |
---|---|---|---|---|---|---|---|
Amazon Linux |
2018.03 |
2018.03, 2023 |
2, 2023 |
||||
Debian Linux |
Not supported |
11 |
|||||
Red Hat Enterprise Linux |
8, 9 |
||||||
Rocky Linux |
8, 9 |
||||||
SuSE |
12, 15 |
15 |
|||||
Ubuntu |
16.04 LTS, 18.04 LTS |
18.04 LTS, 20.04 LTS |
18.04 LTS, 20.04 LTS, 22.04 LTS, 24.04 LTS |
20.04 LTS, 22.04 LTS, 24.04 LTS |
|||
Windows Server |
2016, 2019, 2022 |
2019, 2022 |
Web and Java agents
The following table summarizes the minimum recommended version of web and Java agents:
Agent | Version |
---|---|
Web agents |
2023.11.2 |
Java agents |
2023.11.2 |
AM supports several versions of web agents and Java agents. You can find information about supported container versions and other platform requirements related to agents in the Web Agents Release Notes and the Java Agents Release Notes.
Java
PingAM software is supported on the following Java environments:
Vendor | AM 7.0 | AM 7.1 | AM 7.2 | AM 7.3 | AM 7.4 | AM 7.5 | AM 8.0 |
---|---|---|---|---|---|---|---|
OpenJDK (1) |
11 |
11, 17 |
17 |
17, 21 |
|||
Oracle Java |
11 |
11, 17 |
17 |
17, 21 |
(1) AM supports OpenJDK-based distributions, including:
-
AdoptOpenJDK/Eclipse Temurin Java Development Kit (Adoptium)
-
Amazon Corretto
-
Azul Zulu
-
Red Hat OpenJDK
Ping Identity tests most extensively with AdoptOpenJDK/Eclipse Temurin. Use the HotSpot JVM, if possible.
Always use a JVM with the latest security fixes. |
Application containers
This table summarizes supported web application containers and their required versions:
Container | AM 7.0 | AM 7.1 | AM 7.2 | AM 7.3 | AM 7.4 | AM 7.5 | AM 8.0 |
---|---|---|---|---|---|---|---|
Apache Tomcat |
8.5, 9 |
10 |
|||||
IBM WebSphere Liberty |
20.0.0.1 |
22.0.0.4 |
24.0.0.6 |
||||
JBoss Enterprise Application Platform |
7.2 |
7.3 |
7.4 |
8.x |
|||
Wildfly |
12, 19 |
15, 19 |
15, 26 |
26 |
30 |
The web application container must be able to write to its own home directory, where AM stores configuration files.
Java Agents and Web Agents require the WebSocket protocol to communicate with AM. Make sure the container where AM runs, the web server/container where the agents run, and your network infrastructure all support the WebSocket protocol. Read your network infrastructure and web server/container documentation for more information about WebSocket support. |
Identity stores
This table lists the supported directory servers for storing AM identities.
You can find information on configuring these directory servers in identity stores.
|
Directory server | AM 7.0 | AM 7.1 | AM 7.2 | AM 7.3 | AM 7.4 | AM 7.5 | AM 8.0 |
---|---|---|---|---|---|---|---|
Embedded PingDS (1)(2) |
7.0 |
7.1.5 |
7.2 |
7.3 |
7.4 |
7.5 |
N/A |
External PingDS (2) |
Any Ping Identity-supported version |
6 and later |
7.3 and later |
||||
Oracle Unified Directory |
11g R2 |
12c |
|||||
Oracle Directory Server Enterprise Edition |
11g |
N/A |
|||||
Microsoft Active Directory |
2016, 2019 |
2019, 2022, 2025 |
|||||
IBM Tivoli Directory Server |
6.4 |
N/A |
(1) Demo and test environments only in AM 7.x. Unsupported since AM 8.
(2) PingDS, formerly named ForgeRock Directory Server.
Third-party software
Ping Identity supports using the following third-party software when logging Common Audit events:
Software | Version (supported from AM 7.0) |
---|---|
Java Message Service (JMS) |
2.0 API |
MySQL JDBC Driver Connector/J |
8 (at least 8.0.19) |
Splunk |
8.0 (at least 8.0.2) |
Elasticsearch and Splunk have native or third-party tools to collect, transform, and route logs. Examples include Logstash and Fluentd. Consider using these alternatives as they have advanced, specialized features focused on getting log data into the target system. They decouple the solution from the Ping Identity Platform systems and version, and provide inherent persistence and reliability. You can configure the tools to avoid losing audit messages if a Ping Identity Platform service goes offline, or delivery issues occur. These tools can work with Common Audit logging:
|
Ping Identity supports using the following third-party software when monitoring AM servers:
Software | Version (supported from AM 7.0) |
---|---|
Grafana |
5 (at least 5.0.2) |
Graphite |
1 |
Prometheus |
2.0 |
For hardware security module (HSM) support, AM requires a client library that conforms to the PKCS#11 standard v2.20 or later.
Supported clients
The following table summarizes supported clients:
Client Platform | Native Apps(1) | Chrome(2) | Edge(2) | Firefox(2) | Safari(2) | Mobile Safari |
---|---|---|---|---|---|---|
Windows 8 |
|
|
|
|||
Windows 10 |
|
|
|
|
||
Mac OS X 10.11 or later |
|
|
|
|
||
Ubuntu 14.04 LTS or later |
|
|
|
|||
iOS 9 or later |
|
|
|
|||
Android 6 or later |
|
|
(1) Native Apps is a placeholder to indicate the platform is not limited to browser-based technologies. An example of a native app would be something written to use common REST APIs.
(2) Latest stable versions are supported.