DB connection password not saved

[_AnonymousUser]

Hi,
I run Open Data Integration v5.5.1 in x86_64 Debian GNU/Linux in order to import a project from a third party just modifying its connection parameters and I am having a strange issue when changing Metadata/DB Connections: the password seems to be not kept after closing the edit window. As per the "Check" button, the modified connection is initially fine, but after propagating the changes to the jobs and closing the assistant, running the jobs yield an Oracle DB connection error due to wrong credentials. When I edit again the connection parameters it turns out that the password has been changed (presumably to the project's default) as the "Check" button and the number of asterisks in the password field show.
Please can someone guide me to debug this issue?
Thanks in advance,
Antonio 

[Anonymous]

Hi Antonio,
Usually this is not expected, something is missing...Can you try checking without password field or set password field as string... you can get confirmation...
Vaibhav

[Anonymous]

Hi Antonio,
Do your DB connection password include backslashes?
Best regards
Sabrina

[_AnonymousUser]

Hi Antonio,
Do your DB connection password include backslashes?
Best regards
Sabrina

Hi Sabrina,
No, just alphas.
Digging a bit more I found that saving parameters as context keep them right through subsequent edits ("check" button confirms this) but they still fail when running the jobs.
Best regards,
Antonio

[_AnonymousUser]

Hi Antonio,
Usually this is not expected, something is missing...Can you try checking without password field or set password field as string... you can get confirmation...
Vaibhav

Hi Vaibhav,
How can I do that? Password is mandatory for that project as it must connect to a remote Oracle server and the field format is hardcoded into the DB connect form, isn't it?
Regards,
Antonio

[Anonymous]

Hi,
Would you mind checking if your database password contained a period (.)?

Best regards
Sabrina

[_AnonymousUser]

Hi,
As I said before, the password only contains alphanumerics (mix of uppercase/lowercase letters plus digits). No special/"strange" characters.
Regards,
Antonio

[Anonymous]

Hi,
Does this issue repro on other bulid version? Could you please elaborate your case with an example for your password which contains only alphanumerics (mix of uppercase/lowercase letters plus digits) so that we can make a testing for you.
Best regards
Sabrina

[Anonymous]

Hi,
By now I can provide you with the two .item connection files (both original and modified) for you to compare. Please notice that for security reasons the server IP, SID and USERNAME have been ofuscated in both files. Nevertheless, the hashed passwords (both default and modified) have been left as they are.
OTOH the failure seems to happen only with "Oracle with SID"-type connections as "MySQL"-type connections save their modified passwords ok. I also tried the Talend version (5.2.0) used by our third-party provider to create the project and the failure also happens there. Creating a brand new "Oracle with SID" connection and editing it afterwards fails too. However, the provider can modify the connection without any issues, using the Windows version of Talend, thus I suspect there must be some kind of correlation between using Linux/OpenJDK to run Talend and this issue (BTW I cleared IcedTea cache to no avail).
Also notice that the SQL_Syntax attribute has been translated to spanish in the modified file. I don't know whether this is relevant or not.
Kind regards,
Antonio

[Jcs19]

Hi,
As I said before, the password only contains alphanumerics (mix of uppercase/lowercase letters plus digits). No special/"strange" characters.
Regards,
Antonio

I'm pretty sure that the DB save the password (the number of asterisks is random), I think your credentials are wrong
Can you generate the documentation of your job and check the password ? hehe
To do so (desactive "hide password" in the project settings, right click on your job and click generate doc as HTML)

Then compare your password and check if Talend saved it right