doc.signer.certificate.< eSign ID >.password=PKCS12 file password
```
Where XXXXXXX is your eSign ID generated from the Leegality dashboard above. You can configure multiple .pfx files in the same application instance by simply adding multiple configurations.
Where <eSignID> is your eSign ID generated from the Leegality dashboard above. You can configure multiple .pfx files in the same application instance by simply adding multiple configurations.
10. Application will run at **/docsigner**. Please ensure that it does not conflict with any other application.
@@ -36,7 +36,7 @@ Now, whenever a signing request is received for your eSign ID, the document will
You can further configure Automated Signing using Document Signer by creating a passkey for the same in your Leegality Dashboard. Pursuant to the same, users from your Organisational Department would be able to get documents eSigned using Document Signer Certificate either using our API Gateway or using the Leegality Dashboard.
**Logs:** All communication with your application is loggable and is enabled by default. You have option to desable the same but that is not recommended. The logs will be created in catalina.out file in TOMCAT logs Directory. You can also change the destination if you wish so. See this link for more details.
**Logs:** All communication with your application is loggable and is enabled by default. You have option to disable the same but that is not recommended. The logs will be created in catalina.out file in TOMCAT logs Directory. You can also change the destination if you wish so. See this link for more details.
Format: yyyy-MM-dd HH:mm:ss.SSS INFO PID --- [THREAD_NAME] APP_PACKAGE_NAME: Message
