-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Metricbeat : SQL & Oracle Modules] Connection string for Oracle does not handle special characters properly #24609
Comments
Pinging @elastic/integrations (Team:Integrations) |
cc @sayden |
Want to add this for reference as well: #25058 |
This can be a particular case of #30947 |
I see this was closed, however, the |
This now works for the |
Summary
Background:
Valid Characters for Oracle Passwords per
https://docs.oracle.com/en/database/oracle/oracle-database/19/sqlrf/CREATE-USER.html#GUID-F0246961-558F-480B-AC0F-14B50134621C
"Passwords can contain any single-byte, multibyte, or special characters, or any combination of these, from your database character set, with the exception of the double quotation mark (") and the return character. If a password starts with a non-alphabetic character, or contains a character other than an alphanumeric character, the underscore (), dollar sign ($), or pound sign (#), then it must be enclosed in double quotation marks. Otherwise, enclosing a password in double quotation marks is optional. "_
Basically every character except
"
Specifically it looks that
%
and\
are not handled correctly.So the workaround is to not use these characters, unfortunately many of the passwords are machine generated and often contains
%
at the very leastThis can easily be reproduced using the following SQL module and running the test command, an actual connection to Oracle is not required.
Steps to reproduced
modules.d
directory under metricbeat home directory./metricbeat test modules sql -d "*"
sql.yml
The text was updated successfully, but these errors were encountered: