-
Problem report
-
Resolution: Fixed
-
Trivial
-
6.0.4rc1, 6.2.0alpha1
-
Sprint 87 (Apr 2022), Sprint 88 (May 2022), Sprint 89 (Jun 2022), Sprint 90 (Jul 2022), Sprint 91 (Aug 2022)
-
0.5
Problem description: When any parameter of the proxy is updated, then the proxy.tls_psk and proxy.tls_psk_identity fields are updated with empty values. This becomes confusing for the end user once he looks into the corresponding Audit log record.
The above fields should be sent only when their values are actually updated, or when the encryption type is changed from PSK to a non-PSK encryption.
Steps to reproduce:
- Create a passive proxy with both connections to proxy and connections from proxy set to "No encryption"
- Update the port of this proxy
- Check the corresponding audit log record.
Result: the corresponding audit log record shows as if the psk fields were also updated along with the proxy port:
proxy.interface: Updated proxy.interface.port: 10051 => 10055 proxy.tls_psk: ****** => ****** proxy.tls_psk_identity: ****** => ******
Expected: If psk fields were not actually updated, then their values should not be sent, and the corresponding misleading information should not be present in audit log.
- causes
-
ZBX-21491 Can create passive proxy with one character in PSK field
- Closed