Lately I was trying to test a service that was using an OWSM Username Service Token policy using SOAPUI and was getting the below error:
<env:Fault xmlns:ns0="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<faultcode>ns0:InvalidSecurity</faultcode>
<faultstring>InvalidSecurity : error in processing the WS-Security security header</faultstring>
<faultactor/>
</env:Fault>
I had added Basic Authorization with the required credentials.
Well the reason was quite simple.
I had not added the username token to the SOAP Header. Hence it was able to validate the security.
Here is what you must do:
Let the Basic Authorization be as is.
1. Right-click on your request message in SOAPUI
2. Select 'Add WSS Username Token'

3. Select Password Text and click on OK.

You can see that the Token is added to the Header

4. Test
Helpful? Please Comment.
<env:Fault xmlns:ns0="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<faultcode>ns0:InvalidSecurity</faultcode>
<faultstring>InvalidSecurity : error in processing the WS-Security security header</faultstring>
<faultactor/>
</env:Fault>
I had added Basic Authorization with the required credentials.
Well the reason was quite simple.
I had not added the username token to the SOAP Header. Hence it was able to validate the security.
Here is what you must do:
Let the Basic Authorization be as is.
1. Right-click on your request message in SOAPUI
2. Select 'Add WSS Username Token'
3. Select Password Text and click on OK.
You can see that the Token is added to the Header
4. Test
Helpful? Please Comment.
Happy Learning!!