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. Also, you should have full rights on the Trust1Connector service running on your machine. SigningHub will prompt you if any of the above-mentioned prerequisites is 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. TC1 can be used as an alternative to the Go>Sign Desktop for local signing. SigningHub supports the T1C SDK v3.8.6.
Configure a connector, in SigningHub Admin.
Configure a signing profile, in SigningHub Admin.
Add the signing profile to the service plan.
Add the signing server to your enterprise user role.
Sign the document via SigningHub Web.
Make the following configurations to a connector in SigningHub Admin:
In the "Basic Information" section, choose "T1C" as the "Provider".
In the "Details" section, fill in the required fields.
Make the following configurations to a signing profile in SigningHub Admin:
Select the T1C Connector created earlier, in the highlighted field below:
Make the following configurations to a service plan in SigningHub Admin:
In the "Signature" section of the service plan, select and add the earlier configured signing profile, as shown below:
Make the following configurations to a user role in SigningHub Web:
Against your user role, in the "Signing Server Preferences" tab, add the signing server.
To perform T1C signatures, follow the below-mentioned steps:
From the document listing, open a the document having a Signature field that you want to sign.
Double click on the signature field, select the T1C Signing Server.
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.
Click on the "Sign" button.
The system will prompt the user to input the token PIN to authorise the signing process.
After signing the document, you can view "Signature Verification".
If the T1C utility is not running on the user's system, SigningHub will show the below dialog.
If the T1C utility is installed on the user's system, run the utility and click on "Try Again".
If the T1C utility is not installed on the user's system, install the utility by clicking on the "click here" link and then click on "Try Again".
Bulk signing is also supported with the T1C Signing Server.
The signing logs are maintained under "User Activity Logs", "Workflow History", and "Workflow Evidence Report".
T1C supports PDF and XML document signing.