Local-side signing using T1C Server

Introduction

SigningHub supports performing local side signing with Trust1Connector (T1C). For this, SigningHub needs to be registered with the T1C platform, and a T1C connector needs to be created in SigningHub to allow SigningHub to connect with the T1C app. The T1C app has to be installed on your local machine, and the related HSM is attached to it while signing, or the system certificates must be available within the local keystores. Also, you should have full rights to the Trust1Connector service running on your machine. SigningHub will prompt you if any of the prerequisites mentioned above are missing. T1C provides a solution to read the hardware tokens with minimum footprint and installations. It can interact with the hardware tokens by using javascript APIs which are implemented in SigningHub for local signing. SigningHub also supports T1C TrustStore for signing documents using locally stored certificates from keystores on Windows and macOS. (The support for TrustStore requires T1C JS SDK version 3.8.5 or later.) T1C can be used as an alternative to the Go>Sign Desktop for local signing. SigningHub supports the T1C SDK v3.8.6.

---

How it works?

1. Configure a connector, in SigningHub Admin.

2. Configure a signing profile, in SigningHub Admin.

3. Add the signing profile to the service plan.

4. Add the signing server to your enterprise user role.

5. Sign the document via SigningHub Web.

---

Configure a Connector in SigningHub Admin

Make the following configurations to a connector in SigningHub Admin:

1. In the "Basic Information" section, choose "T1C" as the "Provider".

1. In the "Details" section, fill in the required fields.

---

Configure a Signing Profile in SigningHub Admin

Make the following configurations to a signing profile in SigningHub Admin:

1. Select the T1C Connector created earlier, in the highlighted field below:

---

Add Signing Profile to a Service Plan in SigningHub Admin

Make the following configurations to a service plan in SigningHub Admin:

1. In the "Signature" section of the service plan, select and add the earlier configured signing profile, as shown below:

   

---

Add Signing Server to a User Role in SigningHub Web

Make the following configurations to a user role in SigningHub Web:

1. Against your user role, in the "Signing Server Preferences" tab, add the signing server.

   

---

Signing using T1C Server

To perform T1C signatures, follow the below-mentioned steps:

1. From the document listing, open a the document having a Signature field that you want to sign.

2. Double click on the signature field, select the T1C Signing Server.

   
3. Upon selecting the T1C Signing Server, the user consent dialog will appear. It will appear once for each user session. Click on the "Yes" button to proceed.

   
4. If you are using T1C JS SDK version 3.8.5 or above, the system will display the "KeyStore Selection" dialogue box. The user can select whether they would like to sign using a token or the 'TrustStore'. (In case of TrustStore, the system certificates are retrieved from MSCAPI on Windows, and Mac Keychain on macOS)

   
5. Click on the "Sign" button.

6. The system will prompt the user to input the token PIN to authorise the signing process. (The signing PIN functionality is not available for signing via 'TrustStore'.)

   
7. After signing the document, you can view "Signature Verification".

---

1. If the T1C utility is not running on the user's system, SigningHub will prompt the user to check:

   • If the T1C utility is installed on the user's system, run the utility and try signing again. (Make sure that the token is connected, or the certificates are available in the truststore, as per the 'KeyStore Selection'.)

   • If the T1C utility is not installed on the user's system, install the utility by clicking on the "click here" link and then try signing again.

2. Bulk signing is also supported with the T1C Signing Server.

3. The signing logs are maintained under "User Activity Logs", "Workflow History", and "Workflow Evidence Report".

4. T1C supports PDF and XML document signing.

5. The support for TrustStore requires T1C JS SDK version 3.8.5 or later. (For older SDK versions, only token-based signing is supported.)

6. In case of TrustStore, the system certificates are retrieved from MSCAPI on Windows, and Mac Keychain on macOS.