15 years ago
WSS / JMS responses ("incoming") are not decrypted
I don't know whether this is a bug or a missing feature.
In our usecase WSSE is only used for the service-responses ("Incoming from SoapUI perspective").
With http the anwser gets decrypted properly (no problems at all).
In case of JMS NO DECRYPTION TAKES PLACE (no error either.)
i debugged a little bit and the reason is obvious:
there are no "RequestFilters" configured for this task in com.eviware.soapui.impl.wsdl.submit.RequestTransportRegistry.
(Just adding the HttpPackagingResponseFilter does not work -- JMS and HTTP transport differ too much).
Please add the WSS-incoming-handling to JMS-Transport.
oliver
In our usecase WSSE is only used for the service-responses ("Incoming from SoapUI perspective").
With http the anwser gets decrypted properly (no problems at all).
In case of JMS NO DECRYPTION TAKES PLACE (no error either.)
i debugged a little bit and the reason is obvious:
there are no "RequestFilters" configured for this task in com.eviware.soapui.impl.wsdl.submit.RequestTransportRegistry.
(Just adding the HttpPackagingResponseFilter does not work -- JMS and HTTP transport differ too much).
Please add the WSS-incoming-handling to JMS-Transport.
oliver