Set up a Docusign connector

ConductorOne provides identity governance for Docusign. Integrate your Docusign instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests.

This is an updated and improved version of the Docusign connector! If you’re setting up Docusign with ConductorOne for the first time, you’re in the right place.

Capabilities

Resource	Sync	Provision
Accounts
Groups	*
Signing groups
Permission profiles

The Docusign connector supports automatic account provisioning and deprovisioning.

Every Docusign account must be assigned at least one permission profile. If all other permission profiles are revoked, the account will be automatically assigned the DocuSign Viewer profile, which cannot be revoked.

*By default, signing groups are not synced. You can configure the connector to sync signing groups, if desired.

Gather Docusign credentials

Configuring the connector requires you to pass in credentials generated in Docusign. Gather these credentials before you move on.

The Docusign credentials requirements depend on your chosen hosting method:

• Cloud-hosted: You’ll use an OAuth app verification flow we’ve set up for you. No additional credentials are needed. You can skip this section and go straight to the cloud-hosted setup instructions below.

• Self-hosted: You’ll need to create a Docusign app that will be used when setting up the connector. Go on to the next section.

Self-hosted only: Create a Docusign app

A user with access to the Docusign Admin console must perform this task.

1. In the Docusign Admin Console, click Add App and Integration Key.

2. Choose a name for your app, such as “ConductorOne” and click Create App.

3. On the app configuration screen, carefully copy and save the Client ID (also called an integration key).

4. Click Add Secret Key, then carefully copy and save the client secret.

5. In the Redirect URI field, enter any URI of your choice (such as http://example.com/callback) and click Add.

6. Under Authentication, enable Authorization Code Grant.

7. Click Save at the bottom of the page.

Generate an OAuth refresh token

1. Follow the Docusign instructions to generate a refresh token.

That’s it! Next, move on to the connector configuration instructions.

Configure the Docusign connector

To complete this task, you’ll need the Connector Administrator or Super Administrator role in ConductorOne and the relevant set of permissions on your Docusign account:

• To sync access data (READ): Read users, groups, and permissions.

• To sync access data and provision accounts (READ/WRITE): Create users plus read users, groups, and permissions.

Cloud-hosted

Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.

1. In ConductorOne, navigate to Admin > Connectors and click Add connector.

2. Search for Docusign v2 and click Add.

3. Choose how to set up the new Docusign connector:

   • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
   • Add the connector to a managed app (select from the list of existing managed apps)
   • Create a new managed app
4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.

   If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.

5. Click Next.

6. Find the Settings area of the page and click Edit.

7. Optional. Click to Sync signing groups, if desired.

8. Click Login with OAuth.

9. Log in and authorize ConductorOne with your Docusign instance.

10. After authorizing, you’ll be redirected back to the ConductorOne integrations page, where an “Authorized as” message is now printed.

11. Click Save.

12. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

That’s it! Your Docusign connector is now pulling access data into ConductorOne.

Self-hosted

Follow these instructions to use the Docusign connector, hosted and run in your own environment.

When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.

Step 1: Set up a new Docusign connector

1. In ConductorOne, navigate to Connectors > Add connector.

2. Search for Baton and click Add.

3. Choose how to set up the new Docusign connector:

   • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
   • Add the connector to a managed app (select from the list of existing managed apps)
   • Create a new managed app
4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.

   If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.

5. Click Next.

6. In the Settings area of the page, click Edit.

7. Click Rotate to generate a new Client ID and Secret.

   Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Docusign connector deployment:

Secrets configuration

# baton-docusign-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-docusign-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Docusign credentials
  BATON_CLIENTID: <Docusign app client ID>
  BATON_CLIENTSECRET: <Docusign app client secret>
  BATON_REDIRECT_URI: <The redirect URI you entered when setting up the Docusign app>
  BATON_REFRESH_TOKEN: <OAuth 2.0 refresh token>

  # Optional: include if you want ConductorOne to provision access using this connector
  BATON_PROVISIONING: true

  # Optional: include if you want ConductorOne to sync signing groups
  BATON_INCLUDE_SIGNING_GROUPS: true

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-docusign.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-docusign
  labels:
    app: baton-docusign
spec:
  selector:
    matchLabels:
      app: baton-docusign
  template:
    metadata:
      labels:
        app: baton-docusign
        baton: true
        baton-app: docusign
    spec:
      containers:
      - name: baton-docusign
        image: ghcr.io/conductorone/baton-docusign:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-docusign
        envFrom:
        - secretRef:
            name: baton-docusign-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.

2. Check that the connector data uploaded correctly. In ConductorOne, click Applications. On the Managed apps tab, locate and click the name of the application you added the Docusign connector to. Docusign data should be found on the Entitlements and Accounts tabs.

That’s it! Your Docusign connector is now pulling access data into ConductorOne.