Tchater maintenant avec le support
Tchattez avec un ingénieur du support

One Identity Safeguard for Privileged Sessions 7.3.1 - Safeguard Desktop Player User Guide

Summary of changes Features and limitations Installing Safeguard Desktop Player First steps Validating audit trails Replaying audit trails Replaying encrypted audit trails Replaying encrypted audit trails from the command line Replaying audit files in follow mode Searching in the content of the current audit file Search query examples Exporting the audit trail as video Exporting the sound from an audit trail Exporting zat and zatx files Sharing an encrypted audit trail Replaying X11 sessions Exporting transferred files from SCP, SFTP, HTTP, and RDP audit trails Exporting raw network traffic in PCAP format Exporting screen content text Troubleshooting the Safeguard Desktop Player Keyboard shortcuts

Problems in VirtualBox

If the fonts are not displayed correctly, or the Safeguard Desktop Player application crashes when started in VirtualBox, enable 3D acceleration (Machine > Settings > Display > Screen > Enable 3D Acceleration), and install VirtualBox Guest Additions.

If these do not solve the problem, see Force rendering software.

Force rendering software

Some video card drivers might have problems with OpenGL rendering: fonts do not appear correctly, or the Safeguard Desktop Player application crashes when started with warnings about the graphics card. If this happens, Safeguard Desktop Player tries to fall back to software rendering, but it might fail to do so.

To force software rendering, start Safeguard Desktop Player using the Safeguard Desktop Player - software rendering item in your application menu, or with the --software command-line option:

  • Windows: player.exe --software

  • Linux: ./player --software

Cannot import CA certificate

On Microsoft Windows, you cannot import CA certificates from a shared drive.

Copy the certificate to a local folder and import it from there.

Also, you must install the Safeguard Desktop Player application locally, you cannot start the player.exe file from a shared drive.

Logging

The Safeguard Desktop Player application displays important log messages on the Warnings tab. If you increase the log level of the application above the default, additional log messages are also displayed.

Figure 14: Warnings and logs

To specify the log level of the Safeguard Desktop Player application, use the following command-line parameters.

  • -l or --log-level <number>

  • Set the log level of Safeguard Desktop Player:

    • 3 - Default log level.

    • 0 - Completely disables logging.

    • 7 - The is most verbose level, used for debugging.

    For example:

    • Windows: player.exe --log-level 5

    • Linux: ./player --log-level 5

  • -o or --log-output <path-to-logfile>

  • Specify the path and filename of the log file. For example:

    • Windows: player.exe --log-output desktop-player.log

    • Linux: ./player --log-output /tmp/desktop-player.log

  • -s or --log-spec <log-spec>

  • Specify different log levels for certain components of Safeguard Desktop Player. For example:

    • Windows: player.exe --log-level 3 --log-spec "bdp.core:5"

    • Linux: ./player --log-level 3 --log-spec "bdp.core:5"

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation