--- title: Port requirements description: PingAccess uses ports and protocols to communicate with external components. This information provides guidance for firewall administrators to ensure that the correct ports are available across network segments. component: pingaccess version: 8.3 page_id: pingaccess:installing_and_uninstalling_pingaccess:pa_port_requirements canonical_url: https://docs.pingidentity.com/pingaccess/8.3/installing_and_uninstalling_pingaccess/pa_port_requirements.html revdate: March 27, 2025 --- # Port requirements PingAccess uses ports and protocols to communicate with external components. This information provides guidance for firewall administrators to ensure that the correct ports are available across network segments. | | | | - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | Direction refers to the direction of requests relative to PingAccess:- Inbound requests Requests that PingAccess receives from external components. - Outbound requests Requests that PingAccess sends to external components. | | Service | Port details | Source | Description | | -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | PingAccess administrative console | * Protocol HTTPS * Transport TCP * Default port 9000 * Destination PingAccess admin console * Direction Inbound | PingAccess administrator browser, PingAccess administrative application programming interface (API) *(tooltip: \
\

A specification of interactions available for building software to access an application or service.\

\
)* REST calls, PingAccess replica admin and clustered engine nodes | Used for incoming requests to the PingAccess administrative console.Configurable using the `admin.port` property in the `run.properties` file. Learn more in the [Configuration file reference guide](../reference_guides/pa_config_file_ref.html). This port is also used by clustered engine nodes and the replica admin node to pull configuration data using the admin REST API. | | PingAccess cluster communications port | - Protocol HTTPS - Transport TCP - Default port 9090 - Destination PingAccess admin console - Direction Inbound | PingAccess administrator browser, PingAccess administrative API REST calls, PingAccess replica admin and clustered engine nodes | Used for incoming requests where the clustered engines request their configuration data.Configurable using the `clusterconfig.port` property in the `run.properties` file. Learn more in the [Configuration file reference guide](../reference_guides/pa_config_file_ref.html). This port is also used by clustered engine nodes and the replica admin node to pull configuration data using the admin REST API. | | PingAccess engine | * Protocol HTTP or HTTPS * Transport TCP * Default port 3000\* Any additional engine listener ports defined in the configuration must be open as well.* Destination PingAccess engine * Direction Inbound | Client browser, mobile devices, PingFederate engine | Used for incoming requests to the PingAccess runtime engine.Configurable using the `Listeners` configuration page. Learn more in the [PingAccess user interface reference guide](../pingaccess_user_interface_reference_guide/pa_ui_ref_guide.html). | | PingAccess agent | - Protocol HTTP or HTTPS - Transport TCP - Default port 3030 - Destination PingAccess engine - Direction Inbound | PingAccess agent | Used for incoming Agent requests to the PingAccess runtime engine.Configurable using the `agent.http.port` property of the `run.properties` file. Learn more in the [Configuration file reference guide](../reference_guides/pa_config_file_ref.html). | | PingAccess sideband (optional) | * Protocol HTTP or HTTPS * Transport TCP * Default port 3020 * Destination PingAccess engine * Direction Inbound | Sideband client (an API gateway such as Kong Gateway or Apigee) | Used for incoming sideband requests to the PingAccess runtime engine.Configurable using the `sideband.http.port` property of the `run.properties` file. Learn more in the [Configuation file reference guide](../reference_guides/pa_config_file_ref.html). The default value of the sideband.http.enabled property is false. This property must be set to true to configure a sideband client. | | PingFederate traffic | - Protocol HTTPS - Transport TCP - Default port 9031 - Destination PingFederate - Direction Outbound | PingAccess engine | Used to validate OAuth *(tooltip: \
\

A standard framework that enables an application (OAuth client) to obtain access tokens from an OAuth authorization server for the purpose of retrieving protected resources on a resource server.\

\
)* access token *(tooltip: \
\

A data object by which a client authenticates to a resource server and lays claim to authorizations for accessing particular resources.\

\
)* and ID tokens, make Security Token Service (STS) *(tooltip: \
\

An entity responsible for responding to WS-Trust requests for validation and issuance of security tokens used for SSO authentication to web services.\

\
)* calls for identity mediation, and return authorized information about a user.Configurable using the `PingFederate Settings` page within PingAccess. Learn more in the [PingAccess user interface reference guide](../pingaccess_user_interface_reference_guide/pa_ui_ref_guide.html). |