PingAuthorize

System requirements

Make sure that your computing environment meets the system requirements for the PingAuthorize dynamic authorization management software.

Ping Identity has tested and certified the configurations listed on this page for compatibility with PingAuthorize. Variations in operating system versions, service packs, or platform components are generally supported unless they are known to cause issues.

The following requirements apply to both Docker deployments and manual installations.

Platforms

PingAuthorize supports actively maintained versions of the following operating systems:

  • Amazon Linux

  • Canonical Ubuntu LTS

  • Microsoft Windows Server 2022 (Policy Editor not supported)

  • Oracle Linux

  • Red Hat Enterprise Linux ES

  • Rocky Linux

  • SUSE Linux Enterprise

PingAuthorize has been tested with the default configurations of all operating system components. Customized implementations or third-party plugins could affect the deployment of PingAuthorize.

Java Development Kit

Install one of the following versions of the Java Development Kit (JDK) before installing PingAuthorize:

  • Oracle JDK 17 and 21

  • OpenJDK 17 and 21

Because of the number of supported JDK variants, not all of them are listed here. For PingAuthorize to support a JDK, the JDK must:

  • Be built from the OpenJDK codebase.

    Supported OpenJDK distributions include, but aren’t limited to:

    • AdoptOpenJDK/Eclipse Temurin Java Development Kit (Adoptium)

    • Amazon Corretto

    • Azul Zulu

    • Red Hat OpenJDK

  • Use the HotSpot JIT compiler. The JDK cannot use OpenJ9 or other JIT implementations.

  • Comply with the Ping Identity Java Support Policy.

Browsers

The PingAuthorize administrative console is compatible with actively maintained versions of the following web browsers:

  • Google Chrome

  • Mozilla Firefox

  • Microsoft Edge

Databases

The Policy Editor persists its policies, Trust Framework, and versioning data in one of the following policy databases:

  • An embedded, file-based H2 database. The Policy Editor uses this database by default.

  • An external PostgreSQL database.

    Learn more in Setting up a PostgreSQL database.