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 supports IPv4 addressing. There is currently no support for IPv6 addressing. |
System component | Requirements | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Operating systems |
|
||||||||||||
Docker support |
You can find the PingAccess Docker image on DockerHub. Learn more in the Ping Identity DevOps documentation.
|
||||||||||||
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.
|
||||||||||||
Java environments |
|
||||||||||||
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 |
You can find information about configuring a hardware security module (HSM) in Hardware security module providers. PingAccess certifies the following HSMs:
|
||||||||||||
Supported HTTP versions |
|
||||||||||||
OIDC providers |
These are the most common providers. However, Ping Identity strives to support any third-party OIDC-compliant provider.
|