Identity Manager displays warning messages in the web sphere system_out log being unable to decrypt data: "Decryption of the givendata was not successful".

Document ID : KB000050342
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

Warnings such as: "[com.netegrity.crypto.RC2128CBCPKCS5PaddingHandler] Decryption of the given data was not successful." might be seen in your web sphere system out log. Follow this doc to retype the password into the data source connection definition in order for these warnings no to show up in the log.

Solution:

You might be seeing the following warning messages repeating in your web sphere system out log:

2011-05-11 14:06:13,758 WARN [com.netegrity.crypto.RC2128CBCPKCS5PaddingHandler]
Decryption of the given data was not successful. Please check whether the data is correct or if it is already decrypted.
2011-05-11 14:06:13,758 WARN [ims.LLSDK.baseobject]
Exception has occurred while attempting to decrypt untagged data declared as encrypted.
2011-05-11 14:06:14,069 WARN [com.netegrity.crypto.RC2128CBCPKCS5PaddingHandler]
Decryption of the given data was not successful. Please check whether the data is correct or if it is already decrypted.
2011-05-11 14:06:14,070 WARN [ims.LLSDK.baseobject]
Exception has occurred while attempting to decrypt untagged data declared as encrypted.
2011-05-11 14:06:14,135 WARN

This might happen if you recreate your Identity Manager environment ( IME ) and import back your JDBC Data Source Connections. Follow the below procedure to retype the JDBC Data Source password in the property pages in the Web Sphere administration console:

  1. Click on system
  2. Expand JDBC Connection Management
  3. Click on Modify JDBC Connection
  4. Click on the search button
  5. You see all of your JDBC data source connection
  6. For each one of them, open it and re-enter the password for DB user
  7. Once you finished this, click on the Reports tab
  8. Click on the Snapshot Tasks sub-tab
  9. Expand Manage Snapshot Database Connection
  10. Click on Modify Snapshot Database Connection
  11. Click on the search button.
  12. You see all of your JDBC data source connection
  13. For each one of them, open it and re-enter the password for DB user
  14. Restart your Web Sphere application server.

This should remove the warning messages from the log file.