Versions Compared

Old Version 1

changes.mady.by.user Implementation

Saved on

compared with

New Version 2

changes.mady.by.user Implementation

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Prerequisites

  1. Customer should have active DocuSign account

  2. SmartAdvocate is configured and ready to use

Configuration Steps

...

Obtain consent for an individual DocuSign user (for example docusign@somelawfirm.com). All documents will be sent for signing on behalf of this user.

  1. Visit URL to request application consent for user:

    1. https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature%20impersonation&client_id=be23ac0a-211b-46ff-a777-ad93061f0a00&redirect_uri=http://localhost:8080/authorization-code/callback

    2. For TEST account (http://account-d.docusign.com )

    3. For PRODUCTION account (http://account.docusign.com )

  2. Login to DocuSign user account

  3. Click ACCEPT to give a consent for Smart Advocate

    Image Removed

  4. Login to Client DocuSign account, go to Settings → Apps and Keys and copy User ID

    Image Removed

  5. Open Smart Advocate menu Admin -> System Parameters and add filter “DocuSign”

    Image Removed

  6. “DocuSign Impersonated User Id for API” parameter. Copy User ID value from Step d.

  7. Edit “DocuSign Authentication Server for API” parameter.

    1. For TEST account use - account-d.docusign.com

    2. For PRODUCTION account use - account.docusign.com

  8. Edit “DocuSign Notifications listener URL” parameter.

    1. For On-Premise customers (URI in format like https://sa.someserver.com/sasvc/sawebservice.svc/Receiver/DocuSign)

      Customers need to have a valid SSL certificate signed by recognized SSL provider

    2. For Cloud customers (URI in format like https://app.smartadvocate.com/sasvc/sawebservice.svc/receiver/docusign?Name=TenantName).

If Client wants to send documents for signature from Multiple DocuSign accounts, it is necessary to configure DocuSign accounts for all Smart Advocate Users who will send documents:

For EVERY DocuSign user:

...

Login to his DocuSign account and Copy User ID value as in Step 1.d

...

If you are interested in how the integration works or would like to purchase, you may contact your SmartAdvocate Sales Specialist or email Sales@smartadvocate.com, and someone will contact you to discuss further.

Warning

SmartAdvocate does not provide or create DocuSign accounts; you will need to have an account before we can configure this integration.

Prerequisites

Note

The customer should have an active DocuSign account with API-level access. If you do not have API-level access, please get in touch with your DocuSign sales representative or support specialist to assist.

You will need to provide user credentials for the DocuSign account to be used when configuring the integration. One of our team members will reach out as they will need a security code to sign into the DocuSign account to complete the integration configuration.

Multi-User Support

We offer multi-user support if documents are required to be sent on behalf of the individual user rather than the default account. There will be additional configurations that the client will have to perform to make this possible.

Note

The below Allow lists (Whitelist) are for server based clients. This will be configured on behalf of SmartAdvocate for Cloud Based (SaaS )Clients.

Server Based Clients:

Please perform the following configuration:

Kindly have your IT Professional configure Port 443 (or Port 80) on your server https://smartadvocate.atlassian.net/l/c/BkHN739r

Please email Implementation@SmartAdvocate.com once completed.

Info

Please review the information & link below regarding Security for DocuSign eSignature. Also you may have to whitelist the following (If Needed).


https://www.docusign.com/trust/security/esignature

Allow lists for DocuSign eSignature service

Our top priority is to make your DocuSign eSignature experience safe and secure, and it’s our intention to provide the most robust and reliable service possible to enable your business transactions. We also want to proactively share information that may be of interest to you regarding our service and understand the requirement to configure security to the needs of your organization.

DocuSign customers should configure their spam filters and other software to allow for the following allowlisted domains to be accepted. They should also explicitly allow Internet addresses advertised by DocuSign eSignature. It’s important to keep up-to-date with our current IP address ranges.

Domains

We recommend allowlisting all subdomains under the following domains:

  • .docusign.com

  • .docusign.net

DocuSign endpoint IP addresses

If customers only need to allowlist the DocuSign endpoint, the following IP addresses apply:

North America-based and demo accounts (current and continuing):

  • **NEW 209.112.104.1 through 209.112.107.254

  • ​64.207.216.1 through 64.207.219.254

  • 162.248.184.1 through 162.248.187.254

Canada-based accounts (current and continuing):

  • 52.237.17.101

  • 52.237.17.162

  • 52.235.28.220

  • 52.235.31.13

European Union-based accounts (current and continuing):

  • 185.81.100.1 through 185.81.103.254

  • 192.103.120.1 through 192.103.123.254

Australian-based accounts (current and continuing):

  • 13.72.248.93

  • 13.72.249.142

  • 13.70.141.103

  • 13.70.136.159

DocuSign email IP addresses

If customers need to allowlist DocuSign’s email IP addresses, the following apply:

North America-based and demo accounts (current and continuing):

  • **NEW 209.112.104.1 through 209.112.107.254

  • 64.207.216.1 through 64.207.219.254

  • 162.248.184.1 through 162.248.187.254

  • 54.240.32.183

European Union-based accounts (current and continuing):

  • 185.81.100.1 through 185.81.103.254

  • 192.103.120.1 through 192.103.123.254