E-IB: After Tools Upgrade Or JDK Update, Outbound SOAP With WS-Security Digital Signature Fails With "Soap Request Not Signed" Error
(Doc ID 2989220.1)
Last updated on FEBRUARY 20, 2024
Applies to:
PeopleSoft Enterprise PT PeopleTools - Version 8.59 and laterInformation in this document applies to any platform.
Symptoms
After tools upgrade or applied java update (e.g. JDK-11.0.20), when sending SOAP message to 3rd party system required WS-Security digital signature,
the following error occurs.
ERROR
-----------------------
Soap request not Signed. Policy requires signing.
Replication Steps
-----------------------
1. Create a new pksc12 type keystore to replace the interop.jks wss keystore
2. Create a private key on the new wss keystore, alias name match to default local node name, e.g. PSFT_HR
3. Setup any service operation outbound routing to enable WSS digital signature
4. Test sending a message, and then check <PS_CFG_HOME>/webserv/<domain>/applications/peoplesoft/PSIGW.war/WEB-INF/errorlog.html for the error:
org.apache.ws.security.WSSecurityException: PSSignatureAction: password callback failed
...
Caused by: javax.crypto.BadPaddingException: Given final block not properly padded. Such issues can arise if a bad key is used during decryption.
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |