What should I do if my EUM Server is unable to start because of below error?
Error Starting EUM Processor Server | com.google.inject.CreationException: Unable to create injector, see the following errors:
Error in custom provider, com.singularity.ee.util.security.credentialstore.exception.CryptoOperationFailureException: Failed to decrypt: Illegal key size or default parameters
Error in custom provider, com.singularity.ee.util.security.credentialstore.exception.CryptoOperationFailureException: Failed to decrypt: Input length must be multiple of 16 when decrypting with padded cipher.....
Cause And Solution
This error is mostly seen post-upgrade or during upgrades, which stops the EUM upgrade/startup or login process.
This usually happens when encrypted/obfuscated values in the eum.properties are incorrect. In order to fix this, edit your eum.properties file with the properties below and restart your EUM server
1. Change onprem.useEncryptedCredentials=true to false --> onprem.useEncryptedCredentials=false
2. Set the password in plaintext for the below properties:
3. If the upgrade was from 4.0 to 4.5, you might also have to update the password in <eum_server_home>/eum-processor/bin/liquidbase.properties for the password property.
4. Restart the EUM server.
If, however, you cannot use the plaintext passwords and you need to use encrypted passwords, you will need to regenerate the encrypted key for the the database password and obfuscated keys for the credential key. Then, update the eum.properties file and restart the EUM Server. The database password may not be decipherable using the key in use. You can follow the steps below to complete this for this process: