LP 7.4.3 - Has anyone setup and used the DocuSign integration successfully?

RE: LP 7.4.3 - Has anyone setup and used the DocuSign integration successfully?

2024-03-06T10:10:23Z

Has anyone had an experience with a positive result with DocuSign integration?

Using Liferay Community Edition Portal 7.4.3.101 CE GA101 I have configured the DocuSign integration in Sandbox mode and am getting no authentication errors or any other errors both in Liferay Portal and DocuSign dashboard.

Simply the transaction leaves no trace.

Moreover in the in "Digital Signature" Liferay Portal Panel there are no processes in progress:

Any further help will be greatly appreciated.

RE: RE: LP 7.4.3 - Has anyone setup and used the DocuSign integration successfully?

2023-11-14T16:41:28Z

Dear Rahul, thank you very much for your complete response.

Unfortunately I haven't resolved the configuration issue yet.

I ran the following URL without any problems:

https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature%20impersonation&client_id=xxxxxxxx-5f37-4d84-8881-xxxxxxxxxxxx&redirect_uri=https://www.somesite.com

Then under Integrations > Connect, clicked ADD CONFIGURATION and selected Custom:

Please note that I didn't put anything in the various above tabs.

Once I have completed the above consent step and confirmed the previous Liferay configuration with the required CLIENT_ID, INTEGRATION_KEY, and RSA_KEY I restarted the Portal server.

For the Account's Base URI filed I still used the "https://demo.docusign.net" value since I'm in Sandbox environment.

So I tried again to send a document to signature but I still don't get any errors or positive reports in the Liferay log and in the DocuSign dashboard.

And still in "Digital Signature" Liferay Portal Panel there are no processes in progress:

Any further help will be greatly appreciated.

RE: LP 7.4.3 - Has anyone setup and used the DocuSign integration successfully?

2023-11-14T10:46:43Z

Please see the link below to learn more about configuring the Docusign Sandbox or Production with Liferay.
Enabling DocuSign Digital Signatures

In addition to the previously mentioned step from the above link, we may need to take additional steps for successful docusign activity, such as authenticating and authorising the newly created app configuration and integration. There are two primary methods for authenticating and authorising JWT or Adding Request application consent.

This step is necessary for DEV, QA, UAT and PRD environments.

URI Syntax:
Please use the following url form in the browser to add request application consent (please make appropriate changes based on your id and keys).

https://account-d.docusign.com/oauth/auth?
    response_type=code
    &scope=YOUR_REQUESTED_SCOPES
    &client_id=YOUR_INTEGRATION_KEY
    &redirect_uri=YOUR_REDIRECT_URI

Reference Example

https://account-d.docusign.com/oauth/auth?
    response_type=code
    &scope=signature%20impersonation
    &client_id=7c2b8d7e-xxxx-xxxx-xxxx-cda8a50dd73f
    &redirect_uri=http://localhost:8080

Please look for the view that allows or accepts the consent.

Your user will be prompted to sign in to their account and give consent for your app to impersonate them. After your user grants permission, your app will be able to use the OAuth JWT Grant flow to impersonate them and make API calls. A set of query parameters will be returned to the redirect URI; in the JWT flow, these parameters (such as code) are not used.

Note: After clicking Accept, it will redirect to your Liferay environment, or if it does not redirect, it will load a 404 page. You can safely ignore this page and close the tab. Check the server console for any specific errors.

Make any necessary changes to the Docusign production or sandbox environment as well.

Under Integrations > Connect, click ADD CONFIGURATION and select Custom
1. Enter a name for the Setting - again, the name doesn't really matter
2. For URL to Publish, enter your Liferay installation's address + "/o/portal/docusign-status-change"

If Setting up on local environment
Localtunnel : Using DocuSign's Connect functionality is required to automatically have Liferay receive and process envelope updates. If you can't or don't want to go through the trouble of ensuring your local instance is behind HTTPS with a non-self-signed cert, you can use Localtunnel to handle it for you:

Run the command npm install -g localtunnel
While Liferay is running, run the command lt -p 8080

Once we have completed the consent steps and added the necessary Liferay configuration with the required CLIENT_ID, INTEGRATION_KEY, and RSA_KEY. Request that the instance be restarted and that we look for any specific errors in the server console. Providing there are no errors, we may be able to work with Docusign via Liferay.

LP 7.4.3 - Has anyone setup and used the DocuSign integration successfully?

2023-11-13T18:02:03Z

Using Liferay Community Edition Portal 7.4.3.101 CE GA101 I have configured the DocuSign integration in Sandbox mode and am getting no authentication errors. On the contrary, if I use an incorrect RSA Private Key in the Liferay Portal log I receive the "consent_required" error.

However, after sending a document for electronic signature, everything remains unchanged: no Digital Signature Envelope in the Liferay dashboard, no API calls in the DocuSign dashboard and of course no email from DocuSign to sign recipient.

When sending documents to the electronic signature process, no errors appear in the Liferay Portal log.
You only get an error by setting an incorrect RSA Private Key: "consent_required"

Has anyone had an experience with a positive result with DocuSign integration?

I double (and more) checked my configuration parameters and they are correct since they are taken from the DocuSign dashboard:

- API User ID: *************************
- API Account ID: ***************************
- Account's Base URI (https://demo.docusign.net)
- Integration Key: ****************************
- Environment (Sandbox)
- RSA Private Key: ********************************************************

Thanks in advance for any feedback.