Introduction

SigningHub supports local signing through unique RUT values that are exclusively assigned to each user. The users who wish to use the RUT based Go>Sign signing, need to modify the web.config files. The Go>Sign Desktop app has to be installed and should be running on your machine. Your RUT-based certificates that you want to perform signatures with, having the Subject Alternative Name value, must also be installed on your local machine. SigningHub supports the latest version of the Go>Sign Desktop app.


How it works?

  1. Configure a Go>Sign signing profile as a prerequisite, in  ADSS.
  2. Modify the Web.config file, in SigningHub directory.
  3. Configure a connector, in SigningHub Admin.
  4. Configure a signing profile, in SigningHub Admin.
  5. Add the signing profile to the service plan.
  6. Add signing server to your enterprise user role.
  7. Add the National ID to your Profile.
  8. Sign the document via SigningHub Web.


Configure a Go>Sign Profile in ADSS

For local signing with RUT, a Go>sign profile is configured in Go>Sign Service. 


Make the following configurations to a Go>Sign profile:


  1. From the "General" section, copy the Go>Sign Profile ID because it would be used in SigningHub Admin.
  2. In the "Keystore Settings" section, check "OS native API (MS CAPI & Mac Keychain)". 





Modify the Web.config File in SigningHub Directory

To enforce the users to use the RUT values for signing, the Web.config file needs to be modified in the SigningHub Directory.


Make the following modifications to the web.config file:


  1. Change the value of "ValidateRUT" tag to "True". Then save the changes and close the "Web.config" file. 




Configure a Connector in SigningHub Admin

To see in detail, how to create an ADSS Server Connector in SigningHub, click here.

Make the following configurations to a connector in SigningHub Admin:


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



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




Configure a Signing Profile in SigningHub Admin

To see in detail, how to create a signing profile in SigningHub, click here.

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


  1. Paste the earlier copied Go>Sign Profile ID, while creating a Go>Sign Profile in the ADSS, in the highlighted field below:




Add Signing Profile to a Service Plan

To see in detail, how to create a service plan in SigningHub, click here.

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


  1. Select and add the earlier configured Signing Profile, in a service plan in SigningHub Admin, as shown below:




Allow Users to Add National ID

To see in detail, how to configure global settings in SigningHub, click here.

Make the following configurations to global settings in SigningHub Admin:


  1. Check the "Allow Users to Add National ID" checkbox to allow the users to add their National ID to their profiles, as shown below:






Add Signing Server to a User Role in SigningHub Web

To see in detail, how to manage enterprise user roles in SigningHub, click here.

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


  1. Against your user role, in the "Signature Settings" tab, add the signing server.




Add National ID to your Profile

To see in detail, how to manage your profile in SigningHub, click here.

Make the following configurations to your profile in SigningHub Web:


  1. Copy the National ID, which is defined as the value of "Subject Alternative Name" from your certificate, and paste it in the "National ID" field, as shown below:
  1. The National ID can also be provided at the time of new user registration.


Go>Sign Signing via SigningHub Web 

To sign the document via SigningHub Web, follow the below-mentioned steps:


  1. Open SigningHub Web and open a document having a signature field that you want to sign. 
  2. Click on the signature field and select the Go>Sign Signing Server. Upon selecting the signing server, the system will fetch all the certificates which have the same "Subject Alternative Name" value as the National ID, specified in your profile. If a National ID has not been provided or an invalid National ID has been provided, the system will not let the user sign the documents using the ADSS or CSC Signing Servers, given that the "ValidateRUT" tag in the web.config file has been set to "True".



  1. Then click on the signature field and then click "SIGN NOW".



  1. After signing the document, click the three dots menu  and select "Signature Verification" to view the"Signature Verification" details. The signatures are verified through the ADSS verification service.
  1. Go>Sign signing supports PDF and XML document signing. 
  2. The National ID will be validated for both ADSS (as a local signing server) and CSC Signing Servers, if the "ValidateRUT" tag in the web.config file has been set to "True". 



See Also