Skip to main content

Hello I am trying to make a soap call through postman but I get an error that my username or password is incorrect. For username I use the email I have on Docusign and for the password the app password I created from the settings. Is this combination correct?

XML body

 

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ds="http://www.docusign.net/API/3.0">

   <soapenv:Header>

      <wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">

         <wsse:UsernameToken>

            <wsse:Username>myEmail</wsse:Username>

            <wsse:Password>myPassword</wsse:Password>

         </wsse:UsernameToken>

      </wsse:Security>

   </soapenv:Header>

   <soapenv:Body>

      <ds:RequestEnvelope>

         <ds:EnvelopeID>MyEnvelopeId</ds:EnvelopeID>

      </ds:RequestEnvelope>

   </soapenv:Body>

</soapenv:Envelope>

 

For Headers I have

Content-Type : text/xml; charset=utf-8

SOAPAction : RequestStatus

 

 

The error on the response:

    <soap:Body>

        <soap:Fault>

            <faultcode>soap:Client</faultcode>

            <faultstring>One or both of Username and Password are invalid.</faultstring>

            <faultactor>missing in Web.Config</faultactor>

            <detail>

                <ErrorCode xmlns="missing in Web.Config">113</ErrorCode>

                <ErrorReason xmlns="missing in Web.Config">One or both of Username and Password are invalid.</ErrorReason>

            </detail>

        </soap:Fault>

    </soap:Body>

 

Do you known legacy authentication retirement

  • We have set the final date for end-of-life of legacy authentication at September 30th, 2024

https://www.docusign.com/blog/developers/docusign-api-basic-user-password-authentication-retirement

 

FreeLink/甫连信息
🌍 DocuSign Partner | Partner Profile
🏆 2024 APAC Reseller Growth Partner of the Year
🔧 The first in APAC to pass the DocuSign eSignature Technical Consultant certification.
🚀 Expertise in DocuSign integrations with on-premises systems for leading enterprises across various industries.

Feel free to reach out for collaboration opportunities.


But I am using app password authentication that is still supported. The other two header methods are deprecated.

 

If your app doesn’t use OAuth 2.0 to authenticate, you must update it to use OAuth 2.0 (for REST) or App Password (for SOAP) authentication prior to August 2023.

 

Am I wrong regarding this?


it seems app password is still working.

https://developers.docusign.com/docs/esign-soap-api/esign101/auth/app-password-authentication/

could you create a case will support team?

FreeLink/甫连信息
🌍 DocuSign Partner | Partner Profile
🏆 2024 APAC Reseller Growth Partner of the Year
🔧 The first in APAC to pass the DocuSign eSignature Technical Consultant certification.
🚀 Expertise in DocuSign integrations with on-premises systems for leading enterprises across various industries.

Feel free to reach out for collaboration opportunities.


Reply