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:
|
| Service | Port details | Source | Description | ||
|---|---|---|---|---|---|
PingAccess administrative console |
|
PingAccess administrator browser, PingAccess administrative application programming interface (API) REST calls, PingAccess replica admin and clustered engine nodes |
Used for incoming requests to the PingAccess administrative console. Configurable using the 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 |
|
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 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 |
|
Client browser, mobile devices, PingFederate engine |
Used for incoming requests to the PingAccess runtime engine. Configurable using the |
||
PingAccess agent |
|
PingAccess agent |
Used for incoming agent requests to the PingAccess runtime engine. Configurable using the |
||
PingAccess sideband (optional) |
|
Sideband client (an API gateway such as Kong Gateway or Apigee) |
Used for incoming sideband requests to the PingAccess runtime engine. Configurable using the
|
||
PingFederate traffic |
|
PingAccess engine |
Used to validate OAuth access token and ID tokens, make Security Token Service (STS) calls for identity mediation, and return authorized information about a user. Configurable using the |