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_URIReference 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:8080Please 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.