Fixex #4256: Obfuscate JDBC Password in query.log #4261
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixex #4256
To solve the related issue, we suggest the user to use these 2 parameters:
and he agrees with the tip.
In any case, even with these changes, we still need to handle some errors correctly.
Added a custom exception to obfuscate in logs and the returning RuntimeException,
since the connection string may contain the password.
Therefore, executing:
the following exception (and log) will be returned:
instead of the previous one: