Integrating SailPoint with DocuSign eSignature

Use the DocuSign eSignature source to manage identity and access in the DocuSign application. The DocuSign eSignature source securely connects SailPoint with the DocuSign application to load data from the DocuSign application and provision changes to it.

This document is designed to give specific information about the requirements and fields needed to successfully configure an instance of the DocuSign eSignature source.

Supported Features

The DocuSign eSignature connector supports the following features:

• Access Certifications (certifications of entitlements connected to the accounts)
• Add and Remove Entitlement
• Aggregation of Accounts
• Aggregation of Groups
• Delete Accounts

• Aggregation of Permission Profile as Entitlement

  Note

  • To aggregate, enable the option to Manage Permission Profiles as Entitlements and run entitlement aggregation.
  • To manage the permission profile as an entitlement for existing sources, add the permission profile as entitlement type using the API for Update Source Schema | SailPoint Developer Community.

• Provisioning of Accounts

  • Create

    Note

    For Create Account, the permission profile can be assigned to a user while creating an account and updating an account.

  • Update

    Note

    DocuSign API does not let you update user's email address. Even if you see a successful HTTP response with a 200 code, the user's email address will not get changed. Refer to DocuSign APIs for more information.

Activity Insights

Activity Insights supports activity from DocuSign eSignature and its associated accounts. This allows you to gather account information and activity data from DocuSign eSignature.

Prerequisites

The DocuSign eSignature source supports JSON Web Token (JWT) OAuth 2.0 flow. To connect with DocuSign, you must first create an integration application in DocuSign that provides an integration key and add an RSA key pair to the application. For more information about integration application creation, refer to the "Prerequisites" section of the DocuSign documentation.

You must also get the user's consent for the application created in DocuSign to use the OAuth JWT Grant flow to impersonate that user and make API calls. For more information about requesting application consent, refer to the "Step 1. Request application consent" section of the DocuSign documentation.

For JWT flow, the following scopes are required: signature and impersonation.

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.