Authentication request into a Docker container
Hi all, I'm trying to use SoapUI Open Source to do some simple testing of some web services. Our standard development environment is built inside a docker container. If I enter the WSDL location http://bank:7047/NAV/WS/California/Codeunit/GetNAVData I am prompted for my credentials. However, I get this error returned: Error loading [http://bank:7047/NAV/WS/California/Codeunit/GetNAVData]: org.apache.xmlbeans.XmlException: org.apache.xmlbeans.XmlException: error: Unexpected end of file after null I can enter the same URL into a normal browser window and it retrieves the WSDL. I can also use browser-based tools such as Wizdler to retrieve WSDL and submit "Post" and "Get" transactions. If I access our shared test environment which is NOT in a Docker environment (i.e. just another server on our network), my credentials work fine and the WSDL is returned. I tried a demo of SoapUI Pro, and I was able to get it to work with Docker. I'm just wondering if there's a setting in SoapUI Open source that allows authentication into Docker containers? Thanks, Ron
REST Basic Authentication error at endpoint level
Version 5.2.1 on Windows When I add my HTTP Basic Authentication to individual REST requests, it works fine with my service. When I add the same username and password to my endpoint definition instead, I get an apache.httpclient.ClientProtocolException. Here are the log excerpts (with host names obscured). Note the original project endpoint was localhost:9080 (without authentication required), and the new one with it required is what I'm showing as real-endpoint-server. From SoapUI log: Tue Dec 01 18:35:44 CST 2015:DEBUG:Loading Definition... Tue Dec 01 18:35:44 CST 2015:INFO:Loading schema types from [http://localhost:9080.wadl] Tue Dec 01 18:35:44 CST 2015:INFO:Getting schema http://localhost:9080.wadl Tue Dec 01 18:35:44 CST 2015:DEBUG:Loaded Definition: ok Tue Dec 01 18:36:12 CST 2015:DEBUG:Attempt 1 to execute request Tue Dec 01 18:36:12 CST 2015:DEBUG:Sending request: GET /rbm/vehicle/my-item-number?vin=my-vin HTTP/1.1 Tue Dec 01 18:36:12 CST 2015:DEBUG:Receiving response: HTTP/1.1 401 Not authorized. Authentication required for protected file. Tue Dec 01 18:36:12 CST 2015:DEBUG:Connection can be kept alive indefinitely Tue Dec 01 18:36:12 CST 2015:DEBUG:Target requested authentication Tue Dec 01 18:36:12 CST 2015:DEBUG:Authorization challenge processed Tue Dec 01 18:36:12 CST 2015:DEBUG:Authentication scope: BASIC 'Renew_by_Mail'@real-endpoint-server:443 Tue Dec 01 18:36:12 CST 2015:INFO:real-endpoint-server:443 requires authentication with the realm 'Renew_by_Mail' Tue Dec 01 18:36:12 CST 2015:DEBUG:Found credentials Tue Dec 01 18:36:12 CST 2015:DEBUG:Attempt 2 to execute request Tue Dec 01 18:36:12 CST 2015:DEBUG:Sending request: GET /rbm/vehicle/my-item-number?vin=my-vin HTTP/1.1 Tue Dec 01 18:36:18 CST 2015:DEBUG:Connection closed Tue Dec 01 18:36:18 CST 2015:DEBUG:Connection shut down Tue Dec 01 18:36:18 CST 2015:ERROR:Exception in request: org.apache.http.client.ClientProtocolException Tue Dec 01 18:36:18 CST 2015:ERROR:An error occurred [org.apache.http.client.ClientProtocolException], see error log for details Tue Dec 01 18:36:18 CST 2015:INFO:Error getting response for [http://localhost:9080.vehicle:06975686]; org.apache.http.client.ClientProtocolException From error log: Tue Dec 01 18:36:18 CST 2015:ERROR:org.apache.http.client.ClientProtocolException org.apache.http.client.ClientProtocolException at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:822) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754) at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$Helper.execute(HttpClientSupport.java:233) at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport.execute(HttpClientSupport.java:323) at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.submitRequest(HttpClientRequestTransport.java:290) at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.sendRequest(HttpClientRequestTransport.java:220) at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:119) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: org.apache.http.ProtocolException: The server failed to respond with a valid HTTP response at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:109) at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252) at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:281) at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:247) at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:219) at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$SoapUIHttpRequestExecutor.doReceiveResponse(HttpClientSupport.java:147) at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125) at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:633) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:454) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820) ... 11 more However, in http log, it does appear that a reasonable-looking reply was returned, along with a 200 response code. Which also matches my server's http log.
Anybody else having issues with SoapUI 5.2.1 and NTLM?
So, it seems I can't use NTLM anymore inside of SoapUI. What I've done so far: Delete/Reinstall Updated Java to 1.8 and verified via env variable, and start up says it's using java version 1.8.0_111 Tried with Postman (works great) Tried in browser, no problems Tried with WCFStorm.Rest and Windows Authentication and it works. Made sure I'm running the app as "Run as Administrator" Created a new REST Project to make sure things are clean. Deleted the Authentication and reset. Double checked that my account wasn't locked out. (Ok, I'm reaching) I'm specifically getting 401.1 errors if that'd help. This was working at one point. The IIS Server is 10.0, running on Windows 10 Enterprise. if I start SoapUI from the command prompt, I see it starting up. Looking at the IIS log files, it looks like it's not passing my credentials in to be authenticated. I can see where I was using WcfStorm, and when I was just using Chrome. Both passed credentials in. So, anybody got any ideas of what I'm missing? Thanks, NickFacing authentication issue while using soapui for testing
Facing authentication issue while using soapui for testing getting unauthorized response. when preemptives is selected able to see response states 401 page cannot found your unauthorized. this leads me to go for other product like soapsonar which working fine for my requirement. but i am inclined to soapui
http/1.1.407 proxyauthentication required in groovy script
I am trying to trigger the request using HTTPBuilder in groovy script: Here's my script.Here I already defined groovyUtils just not mentioned in code: I am trying to trigger the request using HTTPBuilder in groovy script: Here's my script.Here I already defined groovyUtils just not mentioned in code: String url="http://oba.com" String uriPath="/contact" def req=groovyUtils.getXmlHolder("myReq#request") HTTPBuilder http=new HTTPBuilder(url) http.client.getCredentials( new AuthScope('myProxy',port) new UserNamePasswordCredentials('userName','Password') ) http.setProxy('myProxy',port,'http') http.request(Method.POST,ContentType.XML){ uri.Path=uriPath headers.'user-id'='nbxxx' body:req response.success{resp1,reader-> log.info "$resp1.statusLine" } response.failure{resp1-> log.info "status:$resp1.statusLine" } } but in it is printing that in failure that "http/1.1.407 proxyAuthentication required" why I am getting this. I already mention proxy here