Re: Unable to see SOAP headers while using UsernameToken assertion

I don't see anything immediately wrong from your configuration. Could you create a test-case that I could run to reproduce the problem? Colm. On Thu, Feb 25, 2016 at 2:01 PM, Giriraj Bhojak wrote: > Thanks Colm, I changed the namespace to the one you mentioned. Now I am >

Re: Unable to see SOAP headers while using UsernameToken assertion

Thanks Colm, I changed the namespace to the one you mentioned. Now I am getting similar error, though the stack trace has the class referring to 200702. org.apache.cxf.ws.policy.PolicyException: These policy alternatives can not be satisfied:

Re: Unable to see SOAP headers while using UsernameToken assertion

It looks like you are using the wrong namespace for "sp". It should be: xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702; whereas from the error above it appears that you are using " http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200802;. Colm. On Thu, Feb 25, 2016 at

Re: Unable to see SOAP headers while using UsernameToken assertion

I forgot to mention that I am setting ws-security.username and ws-security.password programmatically onto BindingProvider. Thanks, Giriraj On Feb 24, 2016 11:07 PM, "Giriraj Bhojak" wrote: > Hi, > > I have been trying to use UsernameToken WS-SecurityPolicy assertion, but I

Unable to see SOAP headers while using UsernameToken assertion

Hi, I have been trying to use UsernameToken WS-SecurityPolicy assertion, but I do not see the SOAP headers in the payload. Hence I keep getting the following exception on the server side: org.apache.cxf.ws.policy.PolicyException: These policy alternatives can not be satisfied: