This is where the problem arises:

We have to use a PUBLIC IP for our Docusign Connector url. 

The PC running the import is a firewalled computer

I've allowed the Docusign static ip's through our firewall to that pc only (any port)

Since it is not a public facing machine (or have a public dns entry) I have to use a self-signed certificate. But of course doing that created a cert based on the pc name, and if I check the box for 'Require Server Name Indication' I still have to enter name not ip address as I require on the docusign end.

In theory this could be resolved by you sending DocuSign your certificate, and they could add it to their trusted list. I don't believe that they offer this functionality and instead they require that your certificate be signed by one of the standard CAs. As you say, this requires a dns entry, but to be clear that doesn't require that your internal machine have a public IP. Depending on your exact setup, it might be that the entry resolves to your firewall, which forwards the traffic to the internal server. And one thing to look into and decide is where the decryption happens - at the firewall or on the internal server, or potentially both.

Okay, I got a 90 day cert for testing

Used: https://myserver/DocuSignConnectService/diagnostics/testlogin

for internal test, now I'm getting a new error stating reading/parsing the config.xml

i've attached 2 files, config and eventlog. I can't see what the error is (config is an xml).

Sooo Close

Your configuration is incorrect
- The Laserfiche account and password are missing.
- The port does not need to be 443 but 80
- No need to use TLS

If you want to encrypt the password you have a utility located in ..\Program Files\Laserfiche\Web Import Services\DocuSignConnectService\Config\DocuSignConfigEncryptionToggle.exe

example of configuration that works

<LaserficheServer>localhost</LaserficheServer>
    <LaserfichePortNumber>80</LaserfichePortNumber>
    <LaserficheRepository>Repository</LaserficheRepository>
    <LaserficheUserName>Admin</LaserficheUserName>
    <LaserfichePassword>xxxxxx</LaserfichePassword>
    <LaserfichePasswordEncrypted>false</LaserfichePasswordEncrypted>
    <ACSSharedSecretEncrypted xsi:nil="true" />
    <UseTLS>false</UseTLS>

I hope this can help you

Thanks, we got it working to the point of it needs a license that we were told it didn't, waiting on that to be resolved. As for the port 80 or 443, IIS does have a certificate and bound for 443 and 80 is still bound of course. Guess I'll play with username etc once license is dealt with

@████████ I will need to implement this same solution very soon for a customer and would love to have more information about the license requirement you mentioned. 

1. Was it a DocuSign or Laserfiche license adjustment that was required?
2. In either case, which additional license or license type was required to make this work ?

We're currently under the impression that it is included in our customers current license structure on the Laserfiche side, but I want to be sure that is accurate. 

Thank you all for the helpful thread!

Regarding the license, it is to be purchased from the DocuSign side. The DocuSign add-on provided by Laserfiche does not require a license.

To do your tests you can use the DocuSign SandBox which has the same functionalities as the production platform.
https://go.docusign.com/sandbox/productshot/

DocuSign integration with Laserfiche is done either from the Laserfiche client which sends directly to DocuSign or by using the very rich DocuSign API. This last method requires you to develop your own webservice which will be called via a workflow.

In both cases, "DocuSignConnectService" must be installed to receive signed documents and certificates in Laserfiche.

Samir:

We have a DocuSign acct. I received the 'Updated' license (refreshed in lfds) this am from Laserfiche with a 'Docusign Intergation'. Using the default admin acct in config.xml, tried: http://mypc/DocuSignConnectService/diagnostics/testlogin and it still says 

Not licensed for DocuSign integration. [9179]

Installed on a separate pc from the actual laserfiche server which is supposed to work.