-
Notifications
You must be signed in to change notification settings - Fork 495
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
Obfuscate JDBC Password in query.log #4256
Labels
Comments
vga91
added a commit
that referenced
this issue
Dec 4, 2024
vga91
added a commit
that referenced
this issue
Dec 4, 2024
YYFOmCxC
RobertoSannino
pushed a commit
that referenced
this issue
Dec 6, 2024
vga91
added a commit
that referenced
this issue
Dec 10, 2024
vga91
added a commit
that referenced
this issue
Dec 11, 2024
vga91
added a commit
that referenced
this issue
Dec 17, 2024
vga91
added a commit
that referenced
this issue
Dec 18, 2024
vga91
added a commit
that referenced
this issue
Dec 18, 2024
* [NOID] Fixex #4256: Obfuscate JDBC Password in query.log * [NOID] format changes * [NOID] removed duplicated test and format changes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See trello card
YYFOmCxC
The customer is using a loading script that utilizes APOC.LOAD.JDBC.
When a user uses it, it generates an entry in the query.log files containing its login credential. They need to minimally obfuscate the password.
Although I provided them with the option of configuring aliases in conf/apoc.conf, they deemed this option did not meet their expectations because the password will be hard-written in the apoc.conf file and would like this not to be mentioned anywhere.
Here is their specific feedback:
The text was updated successfully, but these errors were encountered: