Summary
We propose a new feature for QuickFixN to allow sensitive data (e.g., passwords such as tag 554) to be automatically masked or omitted when logging FIX messages with the traditional QF/n ILogFactory implementations.
Motivation
The ILogFactory implementations log all content of the FIX messages to the logging destination, and unless the user has written a custom implementation, that destination is usually plaintext.
It would be very convenient for library users to allow the suppression of sensitive fields (such as 554) from these logs via a configuration setting.
However, given that the logger triggers once for every single message, such filtering must be fast enough to not affect performance.
Proposed Implementation
Configuration Option: Introduce a configuration setting to specify sensitive tags (e.g., tag 554) that should be masked in the logs.
This feature would empower users to control how sensitive data is handled during logging, enhancing both security and developer experience.
Summary
We propose a new feature for QuickFixN to allow sensitive data (e.g., passwords such as tag 554) to be automatically masked or omitted when logging FIX messages with the traditional QF/n ILogFactory implementations.
Motivation
The ILogFactory implementations log all content of the FIX messages to the logging destination, and unless the user has written a custom implementation, that destination is usually plaintext.
It would be very convenient for library users to allow the suppression of sensitive fields (such as 554) from these logs via a configuration setting.
However, given that the logger triggers once for every single message, such filtering must be fast enough to not affect performance.
Proposed Implementation
Configuration Option: Introduce a configuration setting to specify sensitive tags (e.g., tag 554) that should be masked in the logs.
This feature would empower users to control how sensitive data is handled during logging, enhancing both security and developer experience.