-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
fix(user_ldap): Harmonize parameter obfuscation and serialization accross logging methods #53250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…ross logging methods Debug log, profiler and ldap debug log had a different logic for sanitizing of parameters, aligning them. Signed-off-by: Côme Chilliet <[email protected]>
/backport to stable31 |
/backport to stable30 |
/backport to stable29 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fine beside one question
'func' => $functionName, | ||
'args' => json_encode($args), | ||
]); | ||
if ($this->config->getSystemValue('loglevel') === ILogger::DEBUG) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this needed if we then call logger->debug()
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sanitizeFunctionParameters
felt a bit expensive to run for nothing, so I wanted to only use the computing time if the log is actually gonna happen.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually the comment says just that on the line below: /* Only running this if debug loglevel is on, to avoid processing parameters on production */
Summary
Debug log, profiler and ldap debug log had a different logic for
sanitizing of parameters, aligning them.
Checklist