Skip to main content

​
About Docusign

Iru calls the eSignature REST API using OAuth 2.0 JWT Grant: you register an Integration Key (client ID), upload an RSA public key, grant impersonation consent for a service user, and Iru exchanges a signed JWT for access tokens. This suits server-to-server automation without interactive consent each hour.

​
How It Works

DocuSign supports several OAuth 2.0 grant types; for Iru’s server-to-server connector, JWT Grant is the right model: you create an Integration Key (client ID), configure an RSA keypair, grant impersonation consent once for the user Iru acts as, and Iru exchanges a signed JWT for access tokens against the eSignature REST API.
DetailValue
CategoryE-signatures
AuthenticationOAuth 2.0 JWT Grant
High-level steps: Apps and Keys → create Integration Key → JWT auth → generate or upload RSA → capture Integration Key, impersonated user GUID, account base URI, and private key per Iru’s wizard. Official references: Platform auth, JWT Grant, Build integration, eSignature REST.

​
Prerequisites

  • Administrator access in Docusign.
  • developers.docusign.com access to manage integrations.
  • Clear choice of demo vs production keys and OAuth hosts (account-d.docusign.com vs account.docusign.com).

​
Connect Docusign to Iru

Complete this tab before you connect the source in Compliance.
1

Open Apps and Keys

Sign in to the correct Docusign environment (demo vs production). Open Settings → Apps and Keys (wording can vary slightly by account type).
2

Add an app and integration key

Select Add App and Integration Key (or Create app). Name the app so operators recognize it (for example Iru Compliance). Copy the Integration Key; this is your OAuth client ID for JWT.
3

Enable JWT Grant

In the app’s authentication settings, enable JWT Grant for server-to-server use. Save changes if Docusign prompts you.
4

Generate or upload RSA keys

Under Service Integration, choose Generate RSA (or upload your public key per Docusign’s docs). Download the private key immediately and store it in a vault. You cannot retrieve the private key from Docusign later.
5

Grant impersonation consent

Open the consent URL Docusign provides for JWT (scopes typically include signature and impersonation). Sign in as the user to impersonate and click Allow. Complete any redirect your app registration requires.
Continue on the Iru Compliance tab.

​
Troubleshooting

Check pop-up blocker settings for the Iru site and try again.
Private key matches uploaded public key; server clock accurate.
Resolve regional restapi host from Docusign account metadata.
Keys and OAuth hosts must match the environment.

​
Considerations

Access tokens expire about hourly: JWT Grant re-runs…

Access tokens expire about hourly - JWT Grant re-runs automatically; protect the RSA private key like a production secret.

Sources Management

Browse and manage every Compliance source.

Getting Started With Compliance

Frameworks, actions, and Artifacts.

Iru Overview

How Endpoint, Compliance, and Identity fit together.

Artifacts Management

Upload, review, and organize evidence from sources and actions.