Hi,
Not sure what you mean by "signed", as actually you needn't sign the
soap request.
Per your server side WSS4JInInterceptor, it expect an UsernameToken ws-
security header, some thing like
<soap:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
">
<wsse:UsernameToken >
<wsse:Username>joe</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText
">password</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</soap:Header>
Does your SOAP request already have this header? Could you post the
SOAP request here?
Freeman
On 2011-11-29, at 下午5:26, Chaks wrote:
Thanks everyone for your inputs.
I have signed the SOAP request and now I can see the Security related
information in the SOAP message, but still getting the same error.
Thanks,
Chaks.
--
View this message in context:
http://camel.465427.n5.nabble.com/Problem-Configuring-WSS4JInInterceptor-Using-a-Blueprint-tp5028621p5031711.html
Sent from the Camel - Users mailing list archive at Nabble.com.
---------------------------------------------
Freeman Fang
FuseSource
Email:[email protected]
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
