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 supports IPv4 addressing. There is currently no support for IPv6 addressing.
| System component | Requirements | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Operating systems |
Note:
PingAccess was tested with default configurations of operating system components. If your organization has customized implementations or has installed third-party plug-ins, deployment of the PingAccess server might be affected.
|
||||||||||||
|
Docker support |
View the PingAccess Docker image on DockerHub. Visit Ping Identity’s DevOps documentation for more information. Note:
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, and Windows Hyper-V. Note:
This list of products is provided for example purposes only. 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 |
Note:
The Ping Identity Java Support Policy applies. For more information, see the Ping Identity Java support policy. |
||||||||||||
|
PingFederate |
The following versions of PingFederate are fully certified with this version of PingAccess:
Other versions of PingFederate are expected to be compatible with this version of PingAccess per Ping'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 |
|
||||||||||||
|
Admin console browsers |
|
||||||||||||
|
Audit event storage (external database) |
|
||||||||||||
|
Hardware security module |
For information about configuring a hardware security module (HSM), see Hardware security module providers. PingAccess certifies the following HSMs:
|
||||||||||||
|
Supported HTTP versions |
|
||||||||||||
|
OpenID Connect (OIDC) providers |
These are the most common providers, however, Ping strives to
support any third-party OIDC-compliant provider.
|