We are sending WS-Security signed SOAP messages. On Oracle JDK the signature validates, but on WebSphere (WAS) the server rejects it as invalid.
The reason: WAS re-serializes the SOAP envelope (com.ibm.ws.webservices.engine.xmlsoap.SOAPEnvelope) and changes prefixes/namespace declarations after signing, then the sign is not valid.
👉 Question: Is there a way to disable this re-serialization, or force WAS to send the signed XML exactly as built?
------------------------------
Jose Luis Nebril
------------------------------
#API-Management
#webMethods
#soa#soap