OAM server is failed to start up correctly and throwing the error 'Caused By: javax.crypto.BadPaddingException: Given final block not properly padded'
(Doc ID 1590687.1)
Last updated on FEBRUARY 22, 2018
Applies to:Oracle Access Manager - Version 220.127.116.11.5 and later
Information in this document applies to any platform.
We have encountered OAM server was failing to start up correctly and throwing the error 'Caused By: javax.crypto.BadPaddingException: Given final block not properly padded'. See below for full stack trace from OAM Diagnostics log:
After following the instructions as mentioned in Doc ID: 1354918.1 - deleting the CSF keys and removing the .oamkeystore file, we were expecting the file to be regenerated on startup. However the AdminServer and oam_server1 managed server both complain that the file could not be found during startup, and the OAM server continues to fail to start.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document