You are viewing limited content. For full access, please sign in.

Question

Question

Docusign Error One or both of Username and Password are invalid.

asked on October 14, 2020 Show version history

In trying to get the docusign integration working I am coming across the following error after selecting a document in the Laserfiche Web Client and clicking the "Request Signature with Docusign" button, selecting the recipients, and then clicking the "Request Signature" button:

 

Error

One or both of Username and Password are invalid.

 

I have correctly set up the the Account ID, User name, and Password here: http://localhost/laserfiche/Configuration/Configuration.aspx#externalSection

DocuSign Integration ON

Account ID 

User name 

Password

 

and I have Validated the DocuSign Account here: /laserfiche/options.aspx?repo=OneidaCounty#/advancedpane

DocuSign Account

Email

Password

 

I have also verified the C:\Program Files\Laserfiche\Web Access\Web Files\Web.config file has the following entry in the <configuration> section:

<system.serviceModel>
    <bindings>
      <basicHttpBinding>
        <binding name="APIServiceSoap">
          <security mode="Transport" />
        </binding>
        <binding name="APIServiceSoap1" />
      </basicHttpBinding>
    </bindings>
    <client>
      <endpoint address="https://www.docusign.net/api/3.0/api.asmx" binding="basicHttpBinding" bindingConfiguration="APIServiceSoap" contract="DocuSignAPI.APIServiceSoap" name="APIServiceSoap" />
    </client>
  </system.serviceModel>

 

And verified that the C:\Program Files\Laserfiche\Web Access\Web Files\web.config has the following entry in the <configuration> section: 

  <!-- WCF client configuration -->
  <system.serviceModel>
    <client configSource="client.config" />
    <bindings configSource="bindings.config" />
    <!-- LMO/IM block -->
    <behaviors configSource="behaviors.config" />
  </system.serviceModel>

 

With client.config having:

<client>
  <!-- Change endpoint address to https://demo.docusign.net/api/3.0/credential.asmx if you're using Demo mode with your own Integrators Key -->
  <endpoint address="https://www.docusign.net/api/3.0/credential.asmx" binding="basicHttpBinding" bindingConfiguration="CredentialSoap" contract="CredentialAPI.CredentialSoap" name="CredentialSoap" />
  <!-- Change endpoint address to https://demo.docusign.net/api/3.0/api.asmx if you're using Demo mode with your own Integrators Key -->
  <endpoint address="https://www.docusign.net/api/3.0/api.asmx" binding="basicHttpBinding" bindingConfiguration="APIServiceSoap" contract="DocuSignAPI.APIServiceSoap" name="APIServiceSoap" />
 

And bindings.config having:

<bindings>
  <basicHttpBinding>
    <binding name="APIServiceSoap" closeTimeout="00:01:00" openTimeout="00:01:00"
        receiveTimeout="00:10:00" sendTimeout="00:01:00" allowCookies="true"
        bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard"
        maxBufferPoolSize="524288" maxBufferSize="50000000" maxReceivedMessageSize="50000000"
        textEncoding="utf-8" transferMode="Buffered" useDefaultWebProxy="true"
        messageEncoding="Text">
      <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384"
          maxBytesPerRead="4096" maxNameTableCharCount="16384" />
      <security mode="TransportWithMessageCredential">
        <transport clientCredentialType="None" proxyCredentialType="None"
            realm="">
          <extendedProtectionPolicy policyEnforcement="Never" />
        </transport>
        <message clientCredentialType="UserName" algorithmSuite="Default" />
      </security>
  </binding>

 

So, I am confused as to why I am presented with this error. Please advise...

0 0

Replies

replied on November 18, 2020

We are still having the same issue. I attended a Consultation Forum Webinar with Alyssa Mathias on Tuesday, November 3, 2020 from which she gave me 3 things to look at:

  1. She pointed out that the client.config file name and location had changed in recent versions to C:\Program Files\Laserfiche\Web Access\Web Files\client.config which I have confirmed is updated properly.
  2. She pointed me to this article https://support.laserfiche.com/kb/1013919/configuration-information-for-tls-1-2 which I followed to update the registry on the server (including a server reboot)
  3. Similar to #2 she pointed me to an answers post https://answers.laserfiche.com/questions/142948/DocuSign-TLS-10-ending-will-the-current-API-still-function#143278 that I also followed.
     

I appreciated these suggestions, but unfortunately they have not changed the issue we are having. Her instructions to me were to try these suggestions and if we were still having difficulties to update and then forward this answers post to support.laserfiche.com so I am doing that now.

 

0 0
replied on April 7, 2022

Good Afternoon Paul,

I'm running into an issue just like this.

Did LF support ever give you a solution to this? Obviously the root issue could be different, but it would be interesting to see what the fix was for you.

0 0
replied on October 17, 2023

To get past my issue I needed to change the server to point to the demo server (since we are using a demo account). But now I am having the same "One or both of Username and Password are invalid" error that PB just posted.

0 0
replied on October 17, 2023

Yes  I am following with Laserfiche Support Team. If anything , will let you know.

If you found anything please do let me know here.

 

Thanks,

Pratik

0 0
replied on October 25, 2023

Any luck about this issue ?


Thanks,

pratik

0 0
replied on October 31, 2023

No progress still

0 0
replied on October 31, 2023

I have same problem and still not resolved problem.

Thanks,

Pratik

0 0
replied on November 2, 2023

Hello Team,

We got resolution after talking with DocuSign Support team. 

++++++++++++++ This is what they suggest++++++++++++++++

Based on the recording the Laserfiche integration is trying to authenticate with DocuSign using Basic Authentication which is a legacy version of Authentication that DocuSign no longer supports in new accounts. 
Basic Authentication means that the authentication request tries to use a username and password in plain text in a header of the HTTP request. 
This article explains this in more detail: https://developers.docusign.com/platform/auth/oauth2-requirements-migration/

Based on the information provided your integration key is 08878771-ae64-4157-8df3-b088989898 and this key is not enabled for Basic Authentication which is why you are running into this error. 

To verify this I've made a change on the integration key and it should now allow the use of Basic Authentication. Can you test and confirm if you still see the error? 

++++++++++++++++++End of suggestion+++++++++++++++++++

Kindly check with developer support team to resolve this problem.

 

Thanks,

Pratik

0 0
replied on October 16, 2023

Hello Sir,

I am facing same problem ; Is there any resolution for that issue.

Thanks,

pratik 

2. Error while requesting signature.png
0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.