PingGateway

Requirements

Ping Identity supports customers using the versions specified here. Other versions and alternative environments might work as well. When opening a support ticket for an issue, however, make sure you can also reproduce the problem on a combination covered here.

Downloads

Download product software from the BackStage download site:

File Description

PingGateway-2024.11.0.zip

Cross-platform distribution including all software components.

PingGateway-sample-application-2024.11.0.jar

Web application for testing PingGateway configurations

For information about using the Docker image provided with the product software, refer to PingGateway’s Deploy with Docker.

Operating systems

Supported operating systems
PingGateway version

Vendor

7.2

2023.11

2024.3

2024.6

2024.9

2024.11

Amazon Linux

(Not supported)

2, 2023

Red Hat Enterprise Linux

7, 8

7, 8, 9

Centos OS

7

Ubuntu LTS

20.04

22.04, 20.04

Windows Server

2016, 2019

2016, 2019, 2022

SUSE Linux Enterprise

12, 15

Rocky Linux

(Not supported)

9.x

Java

PingGateway supports OpenJDK, including OpenJDK-based distributions:

  • AdoptOpenJDK/Eclipse Adoptium

  • Amazon Corretto

  • Azul Zulu

  • Red Hat OpenJDK

Eclipse Adoptium is tested most extensively.

Supported Java versions

PingGateway version

7.2

2023.11

2024.3

2024.6

2024.9

2024.11

Java version

11

17, 11

21, 17

Recommendations:

  • Use the HotSpot JVM.

  • Keep your Java installation updated with the latest security fixes.

  • Java 11 is the earliest long-term supported (LTS) Java version for IG 2023.11 and earlier versions. Earlier versions of Java don’t contain required cryptography fixes. If you are using an earlier version of Java, secure your installation.

HTTP protocol

HTTP/1.1 and HTTP/2.0 are supported. HTTP/1.0 is not supported.

FQDNs

PingGateway replication requires use of fully qualified domain names (FQDNs), such as ig.example.com.

Hostnames like example.com are acceptable for evaluation. In production, and when using replication across systems, you must either ensure DNS is set up correctly to provide FQDNs, or update the hosts file (/etc/hosts or C:\Windows\System32\drivers\etc\hosts) to supply unique, FQDNs.

Certificates

For secure network communications with client applications that you do not control, install a properly signed digital certificate that your client applications recognize, such as one that works with your organization’s PKI, or one signed by a recognized CA.

To use the certificate during installation, the certificate must be located in a file-based keystore supported by the JVM (JKS, JCEKS, PKCS#12), or on a PKCS#11 token. To import a signed certificate into the server keystore, use the Java keytool command.

Third-party software for encryption

Bouncy Castle is required for signature encryption with RSASSA-PSS or Deterministic ECDSA. For information, refer to The Legion of the Bouncy Castle.

Third-party software

Ping Identity provides support for using the following third-party software when logging common audit events:

Software Version

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.

Use these alternatives if possible. These tools 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:

  • Configure the server to log messages to standard output, and route from there.

  • Configure the server to log to files, and use log collection and routing for the log files.

Ping Identity provides support for using the following third-party software when monitoring servers:

Software Version

Grafana

5 (at least 5.0.2)

Graphite

1

Prometheus

2.0

For hardware security module (HSM) support, Ping Identity Platform software requires a client library that conforms to the PKCS#11 standard v2.20 or later.

Studio browser

Many browsers are tested with Studio, including the latest stable version of Chrome.

Features requiring later versions of AM

Feature Minimum version of AM

Session cache eviction.

AM 7.3, available after the IG 2023.2 release

OAuth2TokenExchangeFilter.

AM 7.1

Support for refresh of idle sessions when the SingleSignOnFilter is used for authentication with AM. For more information, refer to the sessionIdleRefresh property of AmService.

AM 6.5.3

Eviction of revoked OAuth 2.0 access tokens from the cache. Learn more from CacheAccessTokenResolver, and the cache property of OAuth2ResourceServerFilter.

AM 6.5.3

Support for OAuth 2.0 Mutual TLS (mTLS). Learn more from ConfirmationKeyVerifierAccessTokenResolver and Validate certificate-bound access tokens.

AM 6.5.1