function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Dev1983Dev1983 

Testing Web Service using SOAP UI V 4.5 hitting HTTPS url.

Dear Experts,

 

I am very new to SFDC and trying to understand some basic features.

I tried to call a sample outofbox Login Web service to generate a session token which can be used for calling custom webservices.

I took the Enterprise WSDL from Setup-Develop-API and imported that in SOAP UI.

While calling this web service I was trying to hit the following URL : https://login.salesforce.com/services/Soap/c/25.0

But this call was getting blocked with following exception : ERROR:java.lang.ClassCastException: org.apache.http.message.BasicHttpRequest cannot be cast to org.apache.http.impl.client.RequestWrapper

 

When I tried to hit the HTTP url (not HTTPS) request was going through but getting following error UNSUPPORTED_CLIENT: HTTPS Required. This means that request was going through but HTTPS was expected. I tried to suppress the setting for HTTPS but could not do so because I am using a developer edition(Administration Set Up ->Session Settings -> Require Secure connections)

 

I need to know can I make a HTTPS call from SOAP UI to a salesforce webservice? If so what extra settings are needed ?

 

Below is my soap request:

 

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:enterprise.soap.sforce.com">
   <soapenv:Header>
     </soapenv:Header>
   <soapenv:Body>
      <urn:login>
         <urn:username></urn:username>
         <urn:password></urn:password>
      </urn:login>
   </soapenv:Body>
</soapenv:Envelope>

 

Much thanks in advance for help.

 

Regards,

Anchal

 

Best Answer chosen by Admin (Salesforce Developers) 
SeAlVaSeAlVa

There is a bug on that version, try downloading 4.0 version and try again

All Answers

SeAlVaSeAlVa

There is a bug on that version, try downloading 4.0 version and try again

This was selected as the best answer
collymitchcollymitch

Thanks for pointing this out it solved the issue for me.

 

As a follow up, this appears to be working now in the nightly build of soapUI version 4.5.1.1