WebService Head Certification

Recent use of JMeter test WebService interface concurrency, call WebService will appear message does not conform to configured policy [Authenticationtokenpolicy (S) ]: No Security Header found such an error.

As a result of the SOAPUI call, the following return appears

This error occurs because the WebService server needs to provide a SOAP-certified header.

For example, you may need to add the following authentication headers:

[HTML]

1. <soapenv:Header>
2. <wsse:security xmlns:wsse= "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd "soapenv:mustunderstand=" 1 ">
3. <wsse:UsernameToken>
4. <wsse:Username>UserName</wsse:Username>
5. <wsse:password type= "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-.0# Passwordtext ">Password</wsse:Password>
6. </wsse:UsernameToken>
7. </wsse:Security>
8. </soapenv:Header>

(This specific format is related to the requirements of the service side, the specific username and pass are also provided by the server)

When the Sopaui is called, the call succeeds, plus a similar.

After the debug is successful in Soapui, copy the corresponding XML to jmeter for use.

WebService Head Certification