DocuSign Integration – R12

NOTE: DocuSign is retiring Basic authentication and enforcing OAuth2.0. Please refer to DocuSign Authentication Using OAuth2.0 for more information.

Overview - DocuSign Integration

The CMiC DocuSign integration provides the easiest and most robust Enterprise electronic signing solution. Layered on top of CMiC ECM (Enterprise Content Management), the solution allows users to quickly prepare documents for signing by selecting project documents and specifying recipients. Then with the click of a button, the documents are locked and transmitted to DocuSign’s eSignature transaction management platform. Recipients are notified to complete the signing process in DocuSign. After completing the signing process, the signed document, with signatures, is made available in CMiC as a new revision. 

Watch this video to learn more about how DocuSign works!

This seamless CMiC eSigning solution simplifies the signing process by:

  • Allowing quick document selection.

  • Specifying recipients either from Project defaults or contacts.

  • Keeping track of both the unsigned and signed versions of the document.

  • Providing the complete signing history.

  • Applying version control.


The following is needed to run the integration successfully:

  1. Appropriate CMiC Field licenses.

  2. A CMiC DocuSign license.

  3. CMiC (R12 or later) configured and running over HTTPS (on port 443).

  4. The server must be running TLS 1.1 or 1.2, however, TLS 1.2 is recommended by CMiC. This is to ensure DocuSign is able to transmit status updates and signed documents back to CMiC (integration will not work with TLS 1.0).

  5. DocuSign licenses (purchased from DocuSign) for each CMiC user that will be sending documents for eSignatures.

  6. Email based login method for DocuSign licenses. It can be set on the System Contact details – External Software Login tab. For details, please refer to CMiC Field Setup.

  7. Any sending user on the project must have the appropriate document security in PM JSP (i.e. must be assigned to a project and must have a project role that allows access to the PM document types being used in the integration).

  8. Ensure the JCE (Java Cryptography Extension) for JDK 1.6 is installed on your server. CMiC DBA Services can assist with this or provide a document with the details.