Securely call the DocuSign digital signature capabilities through the OAuth 2.0
authentication method that is based on the JSON Web Token (JWT) grant.
The following articles explain how to configure your Pega
application to create a JWT with your application's authentication credentials and user
details. Upon request, DocuSign validates the JWT and application permissions, and then
issues an access token that allows use of DocuSign services.
Before you begin: Ensure that you obtained the following integration details
from the DocuSign Developer portal:
Integration key
User ID
RSA private key as a .key extension file
Redirect URI for your integration key, for example
https://<host:port>/prweb/PRRestService/DocuSignService/v1/redirect
The following example shows the DocuSign Developer portal with a sample app and
the integration details that you must provide in your application:For more information, see DocuSign documentation.
Creating a keystore by using OpenSSL
Create a container for the public key certificate that your application uses to
authenticate calls to DocuSign.
Important: This section provides steps on how to generate
the .csr certificate file by using the OpenSSL software. However,
you can use other methods for generating certificates that are more suitable for your
business needs, or that are more compatible with your security standards.
Before you begin: Install or access the preferred certificate generation tool.
For example, for OpenSSL certificate generation, install the OpenSSL software, and then
add OpenSSL to your path environment variables.
In your preferred terminal tool, generate .csr,
.crt, and .p12 files by entering
the following commands:
What to do next: Optionally, you can ensure that your application can
access DocuSign services at all times by monitoring the connection status through the
DocuSign connections landing page. For more information, see Monitoring the DocuSign connection status.