Skip to content

Activity Insights - DocuSign eSignature

To display activity data from DocuSign eSignature, you can set up a single SaaS connector or configure both a virtual appliance (VA) and Activity Insights - DocuSign eSignature connector.

Configuring Activity Insights Using the DocuSign eSignature Connector

If you are using the DocuSign eSignature connector, follow the connector guide to enable Activity Insights.

After a successful test connection, you must correlate accounts and run an aggregation for the DocuSign eSignature source. Your activity data will begin syncing immediately but may take up to 24 hours to display. Data will then update daily.

Note

If you previously configured both the DocuSign eSignature identity governance and Activity Insights - DocuSign eSignature connectors, you do not have to take additional action to continue receiving your data.

Configuring Activity Insights Using a VA-Based Source

If you are setting up Activity Insights using a VA-based connector, you must first create an integration application in DocuSign. You'll then configure both the DocuSign - eSignature identity governance and Activity Insights - DocuSign eSignature connectors so that Identity Security Cloud can gather your account information and display activity data.

Creating an Integration Application in DocuSign

Before activity data can display in Identity Security Cloud, you must create an integration app in DocuSign.

  1. Create or log in to your developer account.
  2. Go to the Apps and Keys page.
  3. Select Add App and Integration Key.
  4. Enter a short, yet descriptive name, for your app and then select Create App.
  5. In the Service Integration section, select + Generate RSA to generate a private key.
  6. Copy the private key to a safe location. You won't be able to access the key again.
  7. In the Additional Settings section, select + Add URI. Enter the URI (http://localhost:8080) where your authenticated users will be redirected.
  8. Select Save at the bottom of the page.

To make API calls using JWT Grant authentication, you must obtain the user’s consent for your app to impersonate them. To obtain this consent, open the following URI in your embedded browser:

1
2
3
4
5
https://base-path/oauth/auth?    
      response_type=code   
      &scope=YOUR_REQUESTED_SCOPES
      &client_id=YOUR_INTEGRATION_KEY
      &redirect_uri=YOUR_REDIRECT_URI

Where:

  • base-path is the base path for the authentication service. This path differs depending on whether your app is in a developer or production environment:

    • For developer environments, replace base-path with account-d.docusign.com.
    • For production environments, replace base-path with account.docusign.com.
  • YOUR_INTEGRATION_KEY is your application's integration key.

  • YOUR_REDIRECT_URI is a redirect URI that matches one of those configured for the application with the specified integration key.
  • YOUR_REQUESTED_SCOPES is a space-delimited list of the scopes. For JWT Grant, this should include the impersonation and signature scopes.

The user is then prompted to sign in to their account and grant consent for their app to impersonate them. After your user grants permission, you can use the OAuth JWT Grant flow to impersonate them and make API calls.

Note

After the user selects Accept, their browser will display a message that the page cannot load. They can safely ignore this page and close the tab.

Configuring the DocuSign eSignature Identity Governance Source

Follow the directions to configure your DocuSign eSignature source in Identity Security Cloud. You can also edit an existing source.

Configuring the Activity Insights - DocuSign eSignature Source

To display activity data from Activity Insights, you must configure the Activity Insights - DocuSign eSignature source in Identity Security Cloud.

  1. Go to Admin > Connections > Sources. 

  2. Select Create New to create a new source. 

  3. Search for and select the Activity Insights - DocuSign eSignature connector.

  4. Enter a name and description for your source. 

  5. In the Source Owner field, enter the name of an owner. Matches appear after you type two letters. 

  6. (Optional) Select a governance group for source management.
  7. Select the checkbox if the source is an authoritative source.
  8. Select Continue to create the source.
  9. Select Configuration from the left panel.
  10. Enter the following information: 
    • API URL - The DocuSign account Base URL, which can be found on the Apps and Keys page.
    • Account ID - The DocuSign Account ID, or external account number (int), which can be found on the Apps and Keys page.
    • Client ID - The client identifier, or integration key, which can be found on the Apps and Keys page.
    • User ID - The User ID of the user being impersonated in the JWT Grant flow. The provided User ID must be in GUID and have obtained the required consent.
    • RSA Private Key - The RSA private key used to generate the digital signature for JWT. The provided key must include the lines -----BEGIN RSA PRIVATE KEY----- and -----END RSA PRIVATE KEY ----- as part of the text.
  11. Select Save to save these settings. 
  12. Select Review and Test from the left panel. 
  13. Select Test Connection to test the connection between the applications. You must have a successful connection for Identity Security Cloud to gather activity data. If the test is unsuccessful, retry your credentials or contact SailPoint Support.

To gather account data, you must correlate accounts and run an aggregation for the DocuSign eSignature identity governance source. Your activity data will begin syncing immediately but may take up to 24 hours to display. Data will then update daily.

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.