Troubleshoot identity connector connectivity
Before you begin:
- Make sure the identity connector status appears as running.
- Enable remote debugging for an identity connector. See Enable or disable remote debugging for a connector.
Note: If an identity connector is
unreachable or Remote Debugging is not enabled, the troubleshooting tools are not
visible for an identity connector.
The identity connectors tab includes common networking tools that allow an administrator to troubleshoot connectivity issues between an identity connector and the directory it’s associated to. Each tool includes a field where administrators can enter information. A terminal window is also embedded in the ETP user interface to show query results.
Each tool includes a field where administrators can enter information.
Troubleshooting tool utility | Description |
---|---|
dig | Queries the DNS server and retrieves information about a hostname such as its resolvable IP address. |
Ping | Determines if the application host or IP address is reachable from the identity connector and available to accept requests. |
Traceroute | Tracks the route that IP packets take from the identity connector to the application host or IP address. |
LFT | Traces the route from the identity connector to the application host or IP address and retrieves additional routing and network information such as the autonomous system (AS) number and detected firewalls. |
cURL | Checks if the application URL is reachable from the identity connector. To troubleshoot application reachability issues, you can use cURL to execute GET and POST requests and inject or add headers to the request. |
While Fiddler is not included as a utility in ETP, you can also download this third-party tool to trace HTTP and HTTPS traffic issues. For more information, see Gather a Fiddler trace.