sk181677 - The "Dst User DN" field in the log details section is not masked

The "Dst User DN" field in the log details section is not masked

Product

Security Management, Smart-1 Cloud

Version

R80.40 (EOS), R81 (EOS), R81.10 (EOS), R81.20

Last Modified

2024-07-01

Symptoms

# grep "dst_user_dn" /var/log/opt/CPrt-<Version>/conf/fieldsConfig.xml

For example:

# grep "dst_user_dn" /var/log/opt/CPrt-R81.10/conf/fieldsConfig.xml

Cause

The file fieldsConfig.xml. is missing the string:

{ "<field name=\"dst_user_dn\" type=\"string\" indexed=\"false\" stored=\"false\" tag=\"identity\" />" }

Solution

This problem was fixed. The fix is included in:

If you choose not to upgrade, Check Point can supply a Hotfix. Contact Check Point Support to get a Hotfix for this issue.

A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix.

For faster resolution and verification, please collect CPinfo files from the Security Management Server and Security Gateways involved in the case.

Hotfix installation instructions:

Refer to sk168597 - How to install a Hotfix.

Important note: You must run this procedure during a maintenance window, as it includes restart of the Check Point services.

Procedure

  1. Close all sessions of the SmartConsole.
  2. Connect to the SSH of the Log Server.
  3. Backup the existing fieldsConfig.xml file:
    # cp /var/log/opt/CPrt-<Your version>/conf/fieldsConfig.xml /var/log/opt/CPrt-R81.10/conf/fieldsConfig.xml.backup
    ```

For Example:
# cp /var/log/opt/CPrt-R81.10/conf/fieldsConfig.xml /var/log/opt/CPrt-R81.10/conf/fieldsConfig.xml.backup
```
  1. Edit the file "fieldsConfig.xml":
    # vi /var/log/opt/CPrt-<Your version>/conf/fieldsConfig.xml
    ```

For example:
# vi /var/log/opt/CPrt-R81.10/conf/fieldsConfig.xml
```
  1. Below the "<fields>" section, add this line:
    <field name="dst_user_dn" type="string" indexed="false" stored="false" tag="identity" />
    ```

6. Save and close the file.
7. Restart Check Point Services:
# cpstop;cpstart
```

NOTE

This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.

Article Properties