Create a T1C Connector

The Trust 1 Connector (T1C) allows SigningHub to connect with the T1C app to perform local signing. T1C provides a solution to read the hardware tokens with a minimum footprint and installation. 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. For this, SigningHub needs to be registered with the T1C platform.

---

Create a T1C connector

1. Click the 'Configurations' option from the navigation panel.

2. Click the 'Connectors' option.

3. Click theicon from the grid header.

   
4. The 'Add' connector screen will appear to add the connector details. It comprises of two sections, i.e. Basic Information and Details. Specify the basic information and click the button to provide the respective connector details.

5. Click the 'Create' button. A new connector will be saved and displayed in the list. See the table below for field descriptions.

Basic Information
Fields	Description
Name	Specify a unique name for this connector, i.e. T1C Solution. This connector will be used in the configuration of Signing Profiles.
Provider	Select the provider for this connector, i.e. "T1C".
Purpose	This field will display the purpose of the selected provider above, i.e. the purpose of "T1C" is "Signing".
Active	Tick this check box to make this connector active. Inactive connectors cannot be configured in the Signing Profiles.

The following table describes the fields on the "Details" section of this screen.

Details
Fields	Description
Logo	Select an appropriate image in the jpeg, jpg, gif or png format for the connector's logo that will be displayed on the login screen.
API Key	Specify the API key that is provided by T1C upon registration, i.e.: 9713945f-3bk2-4674-b50a-j063b6211x6z SigningHub Desktop Web will use this API to communicate with the T1C app.
API URL	The URL that connects to the local Trust1Connector instances. This can be either localhost or a domain that directs towards localhost.
API Port	The port used along with the API URL.
Distribution Service URL	The URL used to fetch the JWT token from the distribution server.