Collecting Logs of Client Components

Axidian Privilege PamSU

Enabling Logging

1. Open the configuration file /etc/pamsu.conf

2. Set the Set log_level parameter to INFO.

   Example

    # Log level is minimum level of logging
    # You can choose beetween
    # INFO, WARN ERROR and FATAL
    Set log_level INFO

3. Save the file.

Collecting Logs

1. Clear existing logs in the folder /opt/Axidian-Privilege/pamsu/logs/
2. Reproduce the problem.
3. Collect an archive with logs and send it to technical support. Describe the user's actions and specify the exact time when the problem occurred.

Axidian Privilege Desktop Console

Enabling Logging

1. Run Axidian Privilege Desktop Console as administrator.
2. Click Tools and go to Options section.
3. Go to the Notifications section in the left menu.
4. Select the Log to application directory checkbox and do not change the current file path.
5. Enable the Debug, Information, Warnings, and Errors logging levels.
6. Click OK.
7. Restart the Axidian Privilege Desktop Console application.

Collecting Logs

1. Clear existing logs in the folder C:\Users[Username]\AppData\Roaming\Axidian Privilege Desktop Console
2. Reproduce the problem.
3. Collect an archive with logs and send it to technical support. Describe the user's actions and specify the exact time when the problem occurred.

Axidian Privilege Web Terminal

Enabling Logging

1. Open the configuration file /etc/axidian/axidian-privilege/web-terminal-proxy/appsettings.json

2. Set the LogLevel parameter to Trace.
   

   Example

   {
     "Settings": {
        "Port": "4822",
        "LogLevel": "TRACE",
        "LogStream": "BOTH",
        "MaxLogFiles": 10,
        "MaxLogFileSize": 1000000
        "Host": "0.0.0.0",
     }
   }

3. Save the file.

4. Navigate to the folder with PAM scripts and restart the component:

   cd /etc/axidian/axidian-privilege/scripts/

   bash restart-pam.sh web-terminal-proxy

Collecting Logs

1. Clear existing logs in the folder /etc/axidian/axidian-privilege/logs/web-terminal
2. Reproduce the problem.
3. Collect an archive with logs and send it to technical support. Describe the user's actions and specify the exact time when the problem occurred.