Jennifer Ruttan wrote
> decrypt automatically via CXF's built-in logic. I receive a
> WSSecurityException ("The signature or decryption was invalid") when I run
> the method on the port that responds with an encrypted MTOM attachment.
The encryption looks standard and if you are able to get the other responses
it suggests it is functioning.
"The signature or decryption was invalid" suggests several things.
CXF as an interpretative tool and may not recognize more than one
ephemeral(secret) key(s) one for the message and one for the MTOM (depends
on their webgate appliance settings). This also suggests WSE and WCF
frameworks in the .NET world would fail.
Possibly a malformed header in the MTOM container.
Order of operation: Whether it is MTOM/encrypted or encrypted/MTOM (huge
impact).
Lastly whether the container is base64 content.
IMHO WSS4J is a red herring.
I would suggest grabbing the MTOM and de-crypto it outside of CXF to see
what you are receiving.
--
View this message in context:
http://cxf.547215.n5.nabble.com/Receiving-and-Decrypting-Encrypted-MTOM-Attachments-tp5733291p5735127.html
Sent from the cxf-user mailing list archive at Nabble.com.
