Hi, I think you should be able to see the decrypted content if you serialize the SOAPMessage object (simply using its writeTo method) after the wss4j's inbound processing, as Dan suggested earlier in this thread.
The serialized message contains tons of wss artifacts and it may appear to be still encrypted but it is decrypted and the decrypted content should be present in the message. If this is really not the case, you should make sure that your interceptor is placed at the right phase. As the wss4j inbound processing is taking place at phase PRE_PROTOCOL, you can place your own logger interceptor at USER_PROTOCOL or POST_PROTOCOL that follows this phase. regards, aki 2011/4/19 Alejandro <[email protected]>: > Sorry doesn't work means that log the message encrypted. > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Log-SoapMessage-After-WSS4J-tp4305812p4314128.html > Sent from the cxf-user mailing list archive at Nabble.com. >
