Log In Using the SOAP API

-

The Bulk API doesn't provide a login operation, so you must use SOAP API to log in.
  1. Create a text file called login.txt containing the following text:
    01<?xml version="1.0" encoding="utf-8" ?>
    02<env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    03    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    04    xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
    05  <env:Body>
    06    <n1:login xmlns:n1="urn:partner.soap.sforce.com">
    07      <n1:username>your_username</n1:username>
    08      <n1:password>your_password</n1:password>
    09    </n1:login>
    10  </env:Body>
    11</env:Envelope>
  2. Replace your_username and your_password with your Salesforce user name and password.
  3. Using a command-line window, execute the following cURL command:
    1curl https://login.salesforce.com/services/Soap/u/48.0 -H "Content-Type: text/xml; charset=UTF-8" -H "SOAPAction: login" -d @login.txt

    The Soap/u/ portion of the URI specifies the partner WSDL. You can use Soap/c/ to specify the enterprise WSDL.

  4. Salesforce returns an XML response that includes <sessionId> and <serverUrl> elements. Note the values of the <sessionId> element and the first part of the host name (instance), such as yourInstance-api, from the <serverUrl> element. Use these values in subsequent requests to the Bulk API.

Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more