It appears that under some circumstances, Denodo is really unable to decrypt the encrypted password from Configurtation.properties file.
From my experience, when encrypt_password.sh return a string containing exclusively alphanumeric characters, there is no issue.
*e.g. : t9N6UnYJN7LV5U82Jtx8RWXC337c3Ph0
However, when the encrypted strings contains oterh characters...
e.g. '+' or '/' or...
then we get the error (probably this is due to the way the encrypted password string is parsed from the configuration file).
After a few attempts, I was able to get a fully alphanumerix encrypted password from encryptpassword.sh on every environments I use.
So, I'm now able to start monitoring processes with the admin password correctly encrypted in the configuration file.
Still, the issue is real.