Connecting SailPoint and DocuSign eSignature

To connect SailPoint with DocuSign eSignature, perform the following tasks:

Adding the Source in SailPoint

To connect to SailPoint, perform the following steps. Once the connection is made, you can configure it to meet your company's needs.

To configure a new source:

1. Sign in to SailPoint.
2. Go to Admin > Connections > Sources.
3. Select Create New.
4. Search for the connector by entering the name in the search box, and then select Actions.

5. In the Actions dropdown list, select the setup method:

   • Express Setup - Quickly create a read-only connection to your target system by providing minimal configurations and authentication. On completion, aggregation is automatically started.

     Note

     Express Setup supports Credential Providers. For information on supported credential providers and configuration, refer to Credential Providers. For more information, contact your SailPoint Customer Service Manager.

   • Standard Setup - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup.

Configuring a Source Using Express Setup

Express Setup minimizes the initial configuration process so you can quickly connect the application and immediately begin aggregating user account and entitlement data.

1. Review the directions and select Start Express Setup.

2. Review the pre-populated Source Name, Source Owner, and Description. To update, select Edit.

   Note

   The source name must be unique. You can change these settings later in the source configuration.

3. (Optional) If enabled for your organization, select the Use a Credential Provider checkbox to manage the source's authentication using a credential provider.

   Note

   To add a Credential Provider in SailPoint, go to Admin > Connections > Credential Providers. For more information about credential providers, refer to Credential Providers.

4. Configure the authentication to allow SailPoint to connect to the source. For more information, refer to the Connection Settings section.

5. Select Finish.

   After a successful test connection, the system creates your source and prompts you to run an aggregation.

   • If you want to aggregate now, select Aggregate.

     • To see the latest account aggregation history, go to Account Management > Account Aggregation.
     • To see the list of aggregated source accounts, go to Account Management > Accounts.

   • If you want to aggregate later, select Exit. This returns you to the Sources page. Your new source is listed, but contains no accounts or aggregation history yet.

Configuring a Source Using Standard Setup

Use Standard Setup to configure the connector for full feature support.

1. In the Source Name field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters.
2. In the Description field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters.
3. In the Source Owner field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to Assigning a Source Owner.
4. (Optional) Select a governance group to grant its members source or role sub-admin level oversight of the source and its access. For more information, refer to Creating and Managing Governance Groups.
5. If this source represents a primary system containing your organization's personnel records, select the Authoritative Source checkbox. For more information, refer to Creating Identity Profiles.
6. Select Continue. The source is created, and you are navigated to the Source Setup > Base Configuration page. Continue to configure your connected source there.

Base Configuration

Provide the base configuration parameters. Information you entered in the Create New Source dialog is automatically entered into the fields in the Base Configuration page. You can edit this information if necessary.

1. Enter a unique name and description for the source.

2. In the Source Owner dropdown list, select the identity that owns this source.

   • To find a source owner, begin entering their name.

3. (Optional) If enabled for your organization, select the Use a Credential Provider checkbox to manage the source's authentication using a credential provider.

   Note

   To add a credential provider, go to Admin > Connections > Credential Providers. For more information about credential providers, refer to Credential Providers.

4. Configure the authentication to allow SailPoint to connect to the source. Refer to Connection Settings for more information.

5. (Optional) In the Governance Group for Source Management dropdown list, select a governance group to associate with this source. For more information about governance groups, refer to Associating Governance Groups with a Source.

6. (Optional) Choose whether to enable or disable provisioning for the source. Provisioning is disabled by default.

   • Enable Provisioning - Set the toggle to Enabled to allow the source to create, update, and deactivate accounts in the connected source system.

   • Disable Provisioning - Set the toggle to Disabled to disable provisioning for the source. Disabling provisioning will prevent the creation, updating, or deactivating of accounts on this source.

7. Select Save.

Connection Settings

You must provide the following information to connect and interact with the DocuSign eSignature application.

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.

1. Select Connection Settings from the menu on the left of the screen.

2. Provide the following information to configure the DocuSign eSignature source:

   • API URL: Provide the DocuSign account base URL.
   • Account ID: Provide the DocuSign external account number (int) or account ID GUID.
   • Client ID: Provide the client identifier or integration key issued to the client during the registration process in the DocuSign application.
   • User ID: Provide the user of the user to be impersonated in the JWT flow. You must provide the User ID in GUID, and you must have the required consent in the DocuSign application.
   • RSA Private Key: Provide the RSA Private Key. You will use this key to generate a digital signature for a JSON Web Token (JWT). The key must include the ----BEGIN RSA PRIVATE KEY---- and ----END RSA PRIVATE KEY---- lines in the text.

3. Select Save.

Activity Insights Settings

SailPoint pulls in activity data in the form of events like user logins, password changes, and content updates within the application. You can view an identity’s activity data within an application to discover trends for that user.

Activity Insights Settings allows you to gather account information and activity data from DocuSign eSignature. To enable Activity Insights for the DocuSign eSignature application, refer to Prerequisites for more information.

To configure Activity Insights, complete the following:

1. Go to Activity Insights Settings.
2. Select Enable Activity Insights to view access to data insights on source and application activity such as logins and other app-specific events.
3. Select Save.

Aggregation Settings

1. In Account Filter, specify the account filter conditions. To apply multiple filters, enter the filter and press the Enter key to add them to the list.

   Available Account Filters

   Attribute Name	Description
   status	Filters results by user account status. A comma-separated list of any of the following: ActivationRequired, ActivationSent, Active, Closed, Disabled. For example, to aggregate accounts that are active, and will have an activation email sent to them; i.e. accounts with an Active and ActivationSent status, you can specify the filter as: status=Active,ActivationSent. Similarly, if you want to filter out accounts with user status as Closed; you can specify the filter as: status=Active,ActivationSent,ActivationRequired,Disabled. This will aggregate all the accounts except the accounts that are in the Closed state.
   email	Filters results based on the email address associated with the user that you want to return. For example, to aggregate accounts that have a specific email, you can specify the filter as: email=abc@example.com
   emailSubstring	Filters results based on a fragment of an email address. For example, when aggregating accounts that have a specific domain, you can specify the filter as: emailSubstring=example.com
   userNameSubstring	Filters the user records returned by the user name or a sub-string of the user name. For example, to aggregate accounts with a sub-string, you can specify the filter as: userSubstring=ab
   groupId	Filters results based on one or more group IDs. For example, to aggregate accounts that are part of a particular groupId, you can specify the filter as: groupId=12345
   notGroupId	Returns user records excluding the specified group IDs. For example, to aggregate accounts that are not part of a particular groupId, you can specify the filter as: notGroupId=12345

   Note

   The email, emailSubstring, userNameSubstring, groupId, and notGroupId filters are only applicable to active users. To get these attributes for a user who is not active, the status filter needs to added along with them. For example, if you want to aggregate the emailSubstring of a user who has status as ActivationSent then you must provide two filters; status=ActivationSent and emailSubstring=example.com

2. In Group Filter, specify the group filter conditions, groupType = AdminGroup. To apply multiple filters, enter the filter and press the Enter key to add them to the list.

   Available Group Filters

   Attribute Name	Description
   groupType	The type of group to return. Valid values: AdminGroup, CustomGroup, EveryoneGroup. For example, to aggregate groups with the group type as AdminGroup, you can specify the filter as: groupType=AdminGroup
   searchText	Filters the results of a GET request based on the text that you specify. For example, to aggregate groups with a specific text, you can specify the filter as: searchText=Finance

3. Select Manage Permission Profiles as Entitlements to include permission profiles in the entitlement aggregation.

4. Select Save.

Review and Test

Perform a test to confirm the connection to SailPoint.

1. Go to Review and Test.

2. Confirm that the entries in each field are correct.

   If you note any mistakes, return to the section and make corrections.

3. Select Test Connection.

SailPoint Application Onboarding

SailPoint application onboarding enables you to easily onboard new applications and create sources following the successful onboarding of a discovery source. To use this feature, continue to Discovered Applications in the SailPoint user interface.

For more information, refer to Application Onboarding in the SailPoint SaaS documentation.

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.