Get extended debug information from the PAM Client or PAM Browser
book
Article ID: 266918
calendar_today
Updated On:
Products
CA Threat Analytics for PAMCA Privileged Access Manager - Server Control (PAMSC)CA Privileged Access Manager (PAM)CA Privileged Identity Management Endpoint (PIM)
Issue/Introduction
The PAM Client the PAM Browser are based upon the Chromium-based JxBrowser. By default, no debug information is provided to the console or the client logs. Use the following steps to enable extended debug information for troubleshooting.
Environment
All versions of Privileged Access Manager (PAM) with the PAM Client installed
TCP Services configured with PAM Browser configured as the Browser Type
Resolution
To obtain extended debug information, follow these steps:
Set Environment Variable: Set the following environment variable to enable the automation port: REMOTE_AUTO_TEST_PORT=9998 (Other port numbers are also possible).
Run the Debug Command: This command will make changes to your system's process execution. Review it carefully before running. Run the following command in a CMD window: "C:\CAPAMClient.exe" -debug -debugBuild -console -devMode -notCombined -notMinified
Additional Information
Interface: Launching the client this way opens a Dev Tools interface to track HTTP traffic. Extended debug info is sent to the PAM Client log and the console.
Performance: Unless troubleshooting REST API calls or extjs issues, the -notCombined and -notMinified options are not required. Excluding them improves performance.
Web Portal Issues: If capturing traffic for a Web Portal issue, close the initial Developer Tools window before calling the Web portal application. A new window will then appear for the specific traffic.
Applet Debug: It is recommended to also enable Applet Debug to provide complementary log messages.