PingAccess

System requirements

Make sure that your system meets the following requirements for PingAccess deployment and configuration.

Ping Identity qualifies the following configurations and certifies that they are compatible with the product. Variations of these platforms, such as differences in operating system version or service pack, are supported until the platform or other required software creates potential conflicts.

PingAccess currently supports IPv4 addressing but not IPv6 addressing.
System component Requirements

Operating systems

  • Amazon Linux 2

    • Amazon Linux 2022

    • Amazon Linux 2023

  • Canonical Ubuntu 20.04 (LTS)

    • Canonical Ubuntu 22.04 (LTS)

  • Microsoft Windows Server 2016 (x64)

    • Microsoft Windows Server 2019 (x64)

    • Microsoft Windows Server 2022 (x64)

  • Oracle Linux 7.9 (Red Hat Compatible Kernel)

    • Oracle Linux 8.6 (Red Hat Compatible Kernel)

  • Red Hat Enterprise Linux ES 7.9

    • Red Hat Enterprise Linux ES 8.8

    • Red Hat Enterprise Linux ES 9.2

  • SUSE Linux Enterprise Server 12 SP5

    • SUSE Linux Enterprise Server 15 SP4

PingAccess was tested with default configurations of operating system components. If your organization has custom implementations or has installed third-party plug-ins, PingAccess server deployment might be affected.

Docker support
Docker version

20.10.17

You can find the PingAccess Docker image on DockerHub and more information in Ping Identity’s DevOps documentation.

Only the PingAccess software is licensed under Ping Identity’s end user license agreement. Any other software components contained within the image are licensed solely under the terms of the applicable open source or third-party license.

Ping Identity accepts no responsibility for the performance of any specific virtualization software and in no way guarantees the performance or interoperability of any virtualization software with its products.

Virtual systems

Although Ping Identity doesn’t qualify or recommend any specific virtual machine (VM) products, PingAccess runs well on several, including:

  • VMWare

  • Xen

  • Windows Hyper-V.

This list of products is provided only as an example. We view all products in this category equally. Ping Identity accepts no responsibility for the performance of any specific virtualization software and does not guarantee the performance or interoperability of any VM software with its products.

Java environments

  • Amazon Corretto 11 (64-bit)

    • Amazon Corretto 17 (64-bit)

    • Amazon Corretto 21 (64-bit)

  • OpenJDK 11 (64-bit)

    • OpenJDK 17 (64-bit)

    • OpenJDK 21 (64-bit)

  • Oracle Java SE Development Kit (JDK) 11 (64-bit)

    • Oracle Java SE Development Kit (JDK) 17 (64-bit)

    • Oracle Java SE Development Kit (JDK) 21 (64-bit)

The Ping Identity Java support policy applies.

Ping Identity intends to remove Java 11 support from PingAccess in December 2025.

PingFederate

The following versions of PingFederate are fully certified with this version of PingAccess:

  • PingFederate 11.3

  • PingFederate 12.0

  • PingFederate 12.1

  • PingFederate 12.2

Other versions of PingFederate are expected to be compatible with this version of PingAccess as described in Ping Identity’s end of life policy.

Some features rely on a specific version of PingFederate to work. This will always be noted in the feature’s description.

End-user browsers

  • Google Chrome

    • Google Android (Chrome)

  • Microsoft Edge

  • Mozilla Firefox

  • Apple Safari

    • Apple iOS (Safari)

Admin console browsers

  • Google Chrome

  • Microsoft Edge

  • Mozilla Firefox

Audit event storage (external database)

  • MS SQL Server 2019

    • MS SQL Server 2022

  • Oracle 19c

  • PostgreSQL 13

    • PostGreSQL 16

Hardware security module

You can find more information about configuring a hardware security module (HSM) in Hardware security module providers. PingAccess certifies the following HSMs:

AWS CloudHSM 5.9.0

AWS CloudHSM is supported with JDK 11. If you plan to use AWS CloudHSM, you must also deploy your environment on a Linux or Windows operating system that is compatible with both PingAccess and AWS CloudHSM.
Thales Luna Cloud HSM Services and Luna Network HSM (Luna HSM Client 10.x)

PingAccess requires you to use Java 8 with Luna HSMs. This is the only exception to PingAccess’s removal of Java 8 support.

Supported HTTP versions

HTTP 1.1

OpenID Connect (OIDC) providers

Ping Identity strives to support any third-party OIDC-compliant provider. The following table includes some of the most common providers used with PingAccess:

Provider Provider Type

PingFederate

PingFederate

PingOne for Enterprise

Common

PingOne SSO

PingOne

PingOne Advanced Identity Cloud

PingOne Advanced Identity Cloud

PingAM

PingAM

Azure

Common

Okta

Common