PingAccess listens for HTTPS requests on the Admin, Engine, and Agent ports in all deployments, and on the Config query port in clustered deployments. See the Clustering in PingAccess reference guide for a comprehensive overview of the steps necessary to set up a clustered environment.

A key pair must be assigned to each listener. By default, the listeners are configured for HTTPS and use pregenerated key pairs associated with localhost.

HTTPS Listener Descriptions
HTTPS Listener Description


Listens for requests for the administrative user interface and the PingAccess REST APIs.


Listens for HTTP or HTTPS requests that are proxied to target web servers associated with Sites. For more information, see Engine listeners.


Listens for requests from PingAccess agents.


Listens for requests from sideband clients.

Config query

Listens for requests for configuration information from replica administrative nodes and engine nodes in clustered deployments.

If you configure a trusted certificate group for a virtual host, or configure an engine key pair to associate it with a virtual host, those settings are used instead of any applicable HTTPS listeners or engine listeners for the virtual host.

Cipher suite ordering for HTTPS listeners

PingAccess supports the use of a defined order for cipher suite usage to help ensure the most secure cipher suites are used first, regardless of the client request. The cipher suite order is defined in <PA_HOME>/conf/ using the tls.default.cipherSuites property.

On new installs, or in the case of an upgrade to release 5.1 or later, this behavior is the default. You can disable this behavior and specify PingAccess to use the order provided by the client by setting useServerCipherSuiteOrder to false using the PingAccess API /httpsListeners endpoint.