How to configure docusign application scope using OAuthJWT?

Hi,

Please find the below steps to configure

  1. Kindly copy the JWT template(Setup) and save the file extension as “. json”
  2. Kindly login to (https://developers.docusign.com/)
  3. Click on the profile and select Myapps & Keys.

  1. If your login for first time, click on “Add app and integration key” and provide app name.
  2. Kindly generate client secret by clicking “add secret key” button under authentication label.

image

  1. Kindly generate private and public key by clicking “Generate RSA” button.

image

  1. Kindly provide below url under redirect uri’s section and click on save

  1. Kindly open saved json template file and modify as per below
    {
    “typ”: “JWT”,
    “alg”: “RS256”,
    “iss”: "3662508e-851e-4b16-b5b0-xxxxxxxxxxxx”, (Kindly copy Integration key)
    “sub”: "0099b00b-990f-4666-98d7-xxxxxxxxxxxx”, (Kindly copy User ID)
    “aud”: “account-d.docusign.com”,
    “scope”: “signature impersonation”,
    “privatekey”: “your private key text” (Kindly copy the private key)

}
Note:

image

Error: - While executing docusign application scope. If your facing application consent error. Kindly follow below steps to avoid this error.

DocuSign?
response_type=code
&scope=YOUR_REQUESTED_SCOPES (signature impersonation)
&client_id=YOUR_INTEGRATION_KEY (Integration key)
&redirect_uri=YOUR_REDIRECT_URI (http://127.0.0.1:10001/authorize/)

Note: - Kindly please add the related information and paste it in chrome browser and hit enter. It will navigate to allow access page. Kindly click on allow.

2 Likes

Excellent write up. Considering the OAUTH2AuthorizatioCode option no longer works properly, this was a life saver. Thank you!

Hi @fernando321 - I’m wondering what issues you’ve seen with the Oauth2AuthorizationCode no longer working properly and if this fit your needs. We’ve had issues with the latest version of the package, required for Windows projects, which requires us to log in with each run manually.

It just would not authenticate no matter what we did. However with this method, everything is working as expected. This use case however is for only one set account, sending out DocuSign instances for signatures (and auto tagging for sign + date here placement). We only had to get the account one time to authorize the signature impersonation once.

If JWT has been correctly configured, the UiPath DocuSign Application Scope should be capable of authenticating automatically.

Can you confirm whether you’re employing JWT within the DocuSign Application Scope?

Yes with JWT. My issue was that the DocuSign activity has two options for authentication, but only the one with JWT actually works. And yes as part of the initial set up there is a step that has to be done manually, once per account on whose behalf you are sending envelopes (https://www.docusign.com/blog/developers/oauth-jwt-granting-consent), or else the DocuSign activity will return an error even with JWT. But once done, you are right, no issues from that point forward with JWT in DocuSign activities.