Docusign: Configuring the Interconnected Apps Integration

Overview

Interconnected Apps provides you with visibility into third-party plugins connected to sanctioned SaaS applications. To provide Cato with visibility of data within an app, you need to set up an integration with the required application. For more information, see Viewing and Analyzing Interconnected Apps.

To configure the Interconnected Apps integration, you need to:

1. Configure the integration within the SaaS application

2. Create the API connector in the Cato Management Application (CMA)

A CASB license is required for Interconnected Apps. For more information about purchasing a CASB license, please contact your Cato representative.

Benefits of Connecting Docusign

After creating this connector, Cato collects and correlates the following data points:

• The integration name and destination website / publish URL

• The envelope and recipient lifecycle events the integration is subscribed to

• Whether the integration receives full signed-document content and form-field values

• A computed risk score and permission level (HIGH / MEDIUM / LOW), derived from the data each integration is authorized to receive

Configuring the Docusign Integration

To configure the Docusign integration, create an application in the DocuSign admin portal.

Prerequisites

• A DocuSign eSignature account with DocuSign Connect (webhooks) available

• The authenticating user must have the Organization Administrator role

Step 1: Configure the Integration in the Docusign Admin Portal

In the Docusign admin portal, configure a user and application.

Creating a User

The first step in configuring the integration is to create a user with the required roles.

To create a user:

1. In the Docusign Admin Portal create a user. For more information, see the Docusign documentation.

2. Assign the user the Organization Administrator or Security Reports Administrator role.

3. On the User's page, copy and save the User ID so that it can be entered into the CMA.

Configure an Application

The next step is to create an Integration key and Private key.

To configure an application:

1. In the Docusign Admin Portal, navigate Settings > Integrations > Apps and Keys.

2. Click Add App and Integration Key.

   

3. Add the following:

   • App Name: Choose a name for the app

   • Integration Type: Third-party integration key

     

   • Redirect URIs: Click Add URI and enter:

     https://cc.catonetworks.com/redirect/cas/appconnector/callback      

   • Allowed HTTP Methods: Check GET and POST        

4. Copy and save the Integration Key so it can be entered into the CMA.

5. In the Service Integration section, click Generate RSA. Copy and save the Private Key so it can be entered into the CMA.

   Note: This is only displayed once.

6. Click Save.

Step 2: Create the API Connector in the CMA

After you have set up an integration with the required application, add the details in the CMA.

To create the API connector in the CMA:

1. From the navigation menu, click Resources > Integrations.

2. Click the Configured Integrations tab.

3. Click New.

   The New Integration panel opens.

4. Select the SaaS Application you want to add.

5. In the Capability drop-down, select 3rd Party Apps.

6. Add the details created during step one.

7. If you are integrating with a development environment, check the Is Dev Environment box, if you are integrating with a production environment, leave this box unchecked.

8. In the Consent Endpoint field:

   • For production environments, add: https://account.docusign.com/

   • For developer environments, add: https://account-d.docusign.com/

9. Click Save.

   The Docusign consent flow opens.

10. Grant consent for these scopes:

    • signature

    • impersonation

11. The app is visible on the Integrated Apps table with a Connected status.