Closed nleach999 closed 1 year ago
@umeshwaghode @nleach999
Is this still an issue? Does this still need a fix?
@cx-scord I have not tried this with any of the latest releases. I would assume it still has an issue.
Hi @cx-scord We have run jasypt encryption on latest cxflow and if we provide proper passphrase and algorithm in double quotes in CLI mode --jasypt.encryptor.password="abcd" --jasypt.encryptor.algorithm="PBEWithMD5AndDES" It's working fine.
Please make sure if you are using any online tool for encrypting password please be sure which algorithm they are using for encryption or decryption.
Description
Jasypt encryption configuration appears to be broken and it appears it has been broken for a long time. Following the configuration instructions in the wiki at the time it was written did work. I tested back to v1.5.4 and the application would not start without the additional configs/workaround.
Expected Behavior
With a Jasypt configuration like this:
and an encrypted value generated per the instructions on the wiki like so:
CxFlow should start and be able to decrypt the encrypted value without needing to provide values that are used for Jasypt encryption (since at runtime CxFlow should only be decrypting).
Actual Behavior
v1.6.34 freezes on start, v1.6.33 and prior exit the application with a message that the password field can't be bound.
Reproduction
v1.6.34
CxFlow 1.6.34 freezes on startup. The last log line with
org.springframework.core.env
logging set toTRACE
is:I attempted to add this missing value (and others) into the yaml config after noticing that Jasypt appears to be looking for several values at start. Adding "missing" config values in v1.6.34 does not work. For v.1.6.34, the only way I could get it to work was to pass the configuration values Jasypt wants on the command line. This is a workaround, but not always ideal:
Without these options passed on the command line, v1.6.34 freezes on startup.
v1.6.33 (and prior)
Startup of v1.6.33 without any additional Jasypt options ends CxFlow execution with this message:
Placing the "missing" Jasypt values in the configuration yaml (as below) allows it to start:
Environment Details
CxFlow v1.6.34 and v.16.33