Forum Discussion
richman555
9 years agoNew Contributor
I have the same issue. The endpoints I am working against validates that there should be no password element passed in the security headers. I am surprised this hasn't been fixed yet. It is a reason my company doesn't use SOAP UI for web service testing.
I have been able to get this working creating my own SOAP Client using Spring WS and WSS4J. It would be wonderful if I could use SOAP UI could add support for this same thing.
Using Spring WS and WSS4J this gets implemented as -
<bean id="wsSecurityUserNameToken" class="org.springframework.ws.soap.security.wss4j.Wss4jSecurityInterceptor">
<property name="securementActions" value="UsernameToken"/>
<property name="securementUsername" value="TestUserName1"/>
<property name="securementPassword" value=""/>
<property name="securementPasswordType" value="PasswordNone>
<property name="securementTimeToLive" value="300>
<property name="futureTimeToLive" value="60>
</bean>- groovyguy9 years agoCommunity Hero
richman555 Try submitting a feature request. ReadyAPI Feature Requests, since it's something doable but currently missing in the product.