Skip to end of metadata
Go to start of metadata

I am unable to publish the updated configurations from SigningHub Admin, what should I do?

There are certain situations when SigningHub Admin does not allow you to publish your updated configurations on SigningHub web. This is mainly because of abrupt unavailability of any of the running SigningHub instances on server. Please ensure the following in order to publish your configurations: 

  • SigningHub Web is accessible on the local machine (server on which it is running).
  • SigningHub API is accessible on the local machine (server on which it is running).
  • SigningHub Core is accessible on the local machine (server on which it is running).
  • The IIS User rights (read and write) have been assigned on SigningHub installation directory, in case you are configuring Enterprise Branding through SigningHub Admin. 

What should be the rights of an IIS user on the SigningHub directory?

When you (IIS User) need to configure Enterprise Branding through SigningHub Admin, you should have the "Read and Write" rights on the "SigningHub" installation directory. You should also have the same rights on the "Temp" and "Framework64" directories as well. 

How to allow Authorised Remote Signing in a service plan?

Authorised Remote Signing (ARS) allows a user to authorise a remote signature (done on server) using their registered mobile device. The device will have its user authentication built-in (touchID or PIN), so in a way they can also configure two-factor authentication. This feature is available in v7.1 or later releases of SigningHub. To allow it in a service plan:

  1. Create a new service plan as required or edit an existing plan
  2. Go to the "Settings Information" tab, tick the "Enable authorised remote signing" checkbox, and save it, see details.
  3. Publish your configurations. 

How to get Google Drive integration information for its connector in SigningHub Admin?

Please follow below steps:

  1. Visit Google Developers website
  2. Go to bottom of the page and select Google API Console
  3. On Google API Console page, select Google Drive API in G Suite section.
  4. Click on Enable button given on Google Drive API page.
  5. Click on Library section from left panel and press create button to create a new project. On New Project page, enter desired name of your project. 
  6. After creating new project, click on Google API icon on left corner to navigate back to API page. Now select Google Drive API, Google Drive API page will be shown to you.
  7. Select Credentials from left panel and select OAuth client ID. Click on Configure consent screen button shown on the next screen to go to Credential screen. Select appropriate options in Application Type, enter Name, other required fields and press Create button. OAuth client ID will be created, client ID and client secret will be displayed to you. Copy and save client ID and client secret to a text file.
  8. Click on Credentials option in left panel and select API key option from Create Credentials dropdown list. API key will be shown to you on screen. Copy and save it.
  9. Login into SigningHub Admin. Go to Configurations --> Connectors and add a new connector. Input name and select Google Drive from Provider dropdown list. In details section, enter client ID, client secret and API key values. Press Save button to save new connector.
  10. Go to Configurations --> Global Settings and select Default Connectors from dropdown list. On Default Connectors page, select newly created Google Drive connector in Default Google Drive connector and save. After successfully saving the configurations, press Publish Changes button on top right corner.

How to get Google Authentication integration information for its connector in SigningHub Admin?

Please follow below steps:

  1. Visit Google Developers website
  2. Go to bottom of the page and select Google API Console
  3. On Google API Console page, select Credentials from left panel.
  4. On Credentials page, select OAuth client ID from Create Credentials dropdown list. Click on Configure consent screen button shown on the next screen to go to Credential screen.
  5. Select/input appropriate options in Application Type, enter Name, other required fields and press Create button. OAuth client ID will be created, client ID and client secret will be displayed to you. Copy and save client ID and client secret to a text file.
  6. Login into SigningHub Admin. Go to Configurations --> Connectors and add a new connector. Input name and select Google from Provider dropdown list. In details section, enter client ID and client secret values. Press Save button to save new connector.
  7. Go to Configurations --> Authentication Profiles and add a new profile. Enter an appropriate name, description, select Google Authentication for Method and select newly created Google Authentication connector from Connector dropdown list. Press Save button to save new profile.
  8. For verification, open login page of SigningHub in any of web browser and click on More Login Options link.  Google authentication option will be displayed to you on pop-up window.

How to get Google reCAPTCHA2 integration information for its connector in SigningHub Admin?

Please follow below steps:

  1. Visit Google reCAPTCHA2 admin panel from link
  2. Login using your account
  3. After successful login, Register a new site page will be displayed. On this page, enter appropriate name in label, select reCAPTCHA v2 and then select Checkbox option. Enter your Domains names in Domains field (one domain name per line), check Term of Service checkbox and press Register button. Once registration process is completed, Site key and Secret key will be displayed on the next page. Copy these value to a text file for later use.
  4. Login into SigningHub Admin. Go to Configurations --> Connectors and add a new connector. Input name and select Google Captcha from Provider dropdown list. In details section, enter Site key and Secret key values. Press Save button to save new connector.
  5. Go to Configurations --> Global Settings and select Default Connectors from dropdown list. On Default Connectors page, select newly created Google Captcha connector in Default Captcha  connector and save. After successfully saving the configurations, press Publish Changes button on top right corner.

How to configure Clickatell connector in SigningHub Admin?

Please follow below steps:

  1. Go to login page of Clickatell: https://www.clickatell.com/sign-in/
  2. Choose your account type:
  3. Developer Central Accounts created before November 2016.
  4. SMS Platform / Touch / Whatsapp Accounts created after November 2016.
  5. Sign in using your respective credentials.
  6. Go to API option, second option from left at the top menu bar.
  7. From the drog down menu of APU option, select Mange API's option.
  8. Select Setup a new API option.
  9. Select the type of API call [HTTP, REST].
  10. The API is generated displaying the relevant details for HTTP and REST calls respectively:
    1. For HTTP:
      1. API ID:       3646497
      2. Name:        HTTP API
      3. Type:          HTTP
      4. user:           asc-sms-gw
      5. password:   <API Password>
      6. api_id:         3646497
      7. to:                <Mobile Number(s)> (comma separated)
      8. text:             <SMS Message>
    Important Note:
    • Go to Edit Settings option.
    • Set up the Username for your API.
    • Set up the Password for your API.
          b. For Rest:
      1. API ID:         3648123
      2. Auth Token: 1fTGBITjToZmf_9NSRkZveX1FiC.cf1XpjQgKDvUibd.wAQyt_4Jt.mzxzVciR
      3. Name:          REST API
      4. Type:            REST
  11. Go to SigningHub Admin-> Configurations-> Connectors.
  12. Select the icon of adding a connector.
  13. In the Add Connector-> Name, give a suitable name for the connector.
  14. Go to Add Connector-> Provider.
  15. From the drop down menu select Clickatell.
    1. Give the following details to complete the configurations of the connector:
    2. Server Address: https://api.clickatell.com/http/sendmsg
    3. API ID:                   [API ID displayed when the new API was created]
    4. User:                      [The Username you setup in Step 8]
    5. Password:              [The Password you setup in Step 8]
  16. Click Finish button.
  17. Publish changes by clicking the PUBLISH CHANGES button.

How to configure Firebase connector in SigningHub Admin?

Please follow below steps:

  1. Go to Firebase developers page: https://console.firebase.google.com
  2. Sign in using your Google credentials.
  3. Select Add Project.
  4. Give appropriate name for your project.
  5. Agree to the controller-controller terms and click Create Project.
  6. Go to your Project -> Project Overview.
  7. Click on the Settings icon next to Project Overview -> Select Project Settings.
  8. Go to Settings -> Cloud Messaging.
  9. The Server Key and Sender ID is displayed for the created project.
  10. Go to SigningHub Admin -> Connectors.
  11. Select the plus sign icon for adding a connector.
  12. Give appropriate name for the connector.
  13. Select Firebase from the Provider drop down menu, click Next button.
  14. Give the Sender ID and Server Key generated in Step 7, click Finish button.
  15. Publish changes by clicking the PUBLISH CHANGES button.

How to configure LinkedIn connector in SigningHub Admin?

Please follow below steps:

  1. Go to LinkedIn developers page: https://developer.linkedin.com
  2. Sign in using your LinkedIn credentials.
  3. From the top menu bar, Select My Apps.
  4. Click on Create Application button.
  5. Give the required details for the application.
  6. Agree to the terms and conditions and click Submit.
  7. The application is created and a Client ID and Client Secret is displayed for the created application.
  8. Go to SigningHub Admin -> Connectors.
  9. Select the plus sign icon for adding a connector.
  10. Give appropriate name for the connector.
  11. Select LinkedIn from the Provider drop down menu, click Next button.
  12. Give the Client ID and Client Secret generated in Step 7, click Finish button.
  13. Publish changes by clicking the PUBLISH CHANGES button.

 

  • No labels