Forum Discussion
lbreuss
12 years agoNew Contributor
pgoovaerts observation is correct. Until it's fixed, you have to use soapUI 4.5.0 for Basic Auth and soapUI 4.5.1 for Keystore Auth. (This should have been caught by a regression test before releasing, shouldn't it?)
@mkoron: Your suggestion for 4.5.1 does not work. My Testcases each already have Preemptive Authentication configured, and setting it in the preferences did not help either.
I use Wireshark to see the traffic. Here are the relevant chunks from the request and response.
Response from JBoss EJB web service: (401 is correct and intended)
The realm in the response is not empty.
Assertions on the HTTP status code don't work in soapUI 4.5.1 when an exception org.apache.http.client.ClientProtocolException occurs. This should succeed, but keeps failing:
Testing with soapUI 4.5.0 the test case succeeds (responseStatusCode == 401 is successfully asserted, no Exception occurs).
@mkoron: Your suggestion for 4.5.1 does not work. My Testcases each already have Preemptive Authentication configured, and setting it in the preferences did not help either.
I use Wireshark to see the traffic. Here are the relevant chunks from the request and response.
Authorization: Basic dXNlcjE6aW52YWxpZHB3
Credentials: user1:invalidpw
User-Agent: Apache-HttpClient/4.1.1 (java 1.5)
Response from JBoss EJB web service: (401 is correct and intended)
HTTP/1.1 401 Unauthorized
Server: Apache-Coyote/1.1
WWW-Authenticate: Basic realm="EJBWebServiceEndpointServlet Realm"
The realm in the response is not empty.
Assertions on the HTTP status code don't work in soapUI 4.5.1 when an exception org.apache.http.client.ClientProtocolException occurs. This should succeed, but keeps failing:
assert messageExchange.responseStatusCode == 401
Testing with soapUI 4.5.0 the test case succeeds (responseStatusCode == 401 is successfully asserted, no Exception occurs).
Related Content
- 4 years agomcbane
- 10 months agojamescollett
- 2 years agoJannord