Introduction

SigningHub gives you an option to pre-authorise users in your Microsoft Active Directory so that they may serve as your registered enterprise users. In this way, your enterprise users can use their Directory credentials (i.e. organizational domain user ID and password) for SigningHub authentication, and wont even need to create their SigningHub IDs. 


How it works?

  1. Configure an Active Directory connector in SigningHub Admin.
  2. Configure the connector in an authentication profile, in SigningHub Admin.
  3. Configure auto provisioning in SigningHub Web.
  4. Configure a security group for auto provisioning.
  5. Auto provision users at the time of login.


Configure a Connector in SigningHub Admin

To see in detail, how to create an Active Directory Connector in SigningHub, click here.

Make the following configurations to a connector in SigningHub Admin:


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



  1. In the "Details" section, fill in the required fields.
  1. This domain user does not necessarily need to have administrator rights in Active Directory. Here are the important considerations about the user connecting with the Domain Controller:
    • Must exist in Active Directory, i.e. a valid Active Directory user.
    • Must be an active user of Active Directory, i.e. should not be set as disabled.
    • Must have the "Read" permissions on Active Directory to read the Security Groups and email addresses of all the users.


Configure an Authentication Profile in SigningHub Admin

To see in detail, how to create an authentication profile in SigningHub, click here.
Make the following configurations to an authentication profile in SigningHub Admin:


  1. Select the Active Directory Connector created earlier, in the highlighted field below:
  1. If you want to allow access to specific authorised security groups in your Active Directory (i.e. Sales, Marketing, Accounts, etc.), enter the name of the security groups, with comma separation, in the "Allowed Groups" field to be used for provisioning in SigningHub.
  2. If the "Allowed Groups" field is left blank, then all the domain users of a directory would be able to authenticate by using the authentication profile.
  3. The "Fully Qualified Domain Name" field refers to the complete domain name that has been configured by your IT Administrator and consists of all the domain users, i.e. mysigninghub.com.


Configure Auto Provisioning in SigningHub Web

To see in detail, how to pre-authorise users in SigningHub, click here.
Make the following configurations in the "Users" tab in SigningHub Web:


  1. In the "Auto Provision Users" section, check the "Automatically register the users" check box and select the "Authentication Profile", created earlier. Click the "Save" button.
  1. All the users that belong to the selected authentication profile will be authorised through Active Directory upon login, and will be automatically registered and activated in SigningHub under the default SigningHub role, provided that provisioning is not enabled by any other enterprise within the same on-premises deployment. 
  2. If multiple enterprises have been configured within an on-premises deployment, then the "Automatically register the users" check box should be ticked for only one enterprise.
  3. Both public and private authentication profiles will be visible in the "Authentication Profile" drop down for pre-authorising users.


Configure a Security Group for Auto Provisioning

SingingHub also allows you to give role based access of SigningHub (i.e. Enterprise Admin, or Enterprise Users, etc.) at Security Group level.


To see in detail, how to manage security groups in SigningHub, click here.

Make the following configurations to a security group in SigningHub Web:


  1. Against a security group. in the "Auto Provision" tab, add the name and role for the security group.
  1. The added security group will be listed inside the Security Group grid. All the users that belong to the security group will be automatically registered and activated in SigningHub, upon login, under the specified role.
  2. The names of the security groups are not validated against the security groups in the Active Directory, at this screen, so it is important that the correct security group name is added for successful pre-authorisation upon login.
  3. In case specific authorised security groups in were allowed in the authentication profile, only the security groups will appear in the "Security Group" drop down.


Auto Provision Users at Login

Logging in through your Active Directory credentials for the first time, will take you to the registration screen and display your Active Directory (email address) for new registration. After registration you can easily login through your Active Directory credentials. However, if the "Automatically register the users" check box is ticked from the "Auto Provision Users" screen, and an Active Directory has been selected as an Authentication Profile, then the registration screen will not be displayed, as the provisioned Active Directory users from there will be automatically registered and activated in SigningHub.


To see in detail, how to login through Active Directory in SigningHub, click here.


  1. From the "More Login Options" option, select  Active Directory.



  1. Provide your Active Directory credentials.



  1. The following login preferences will be followed when logging into SigningHub Web via Active DIrectory:

Login preferences for auto-provisioning

Availability of Security Group in Active Directory

Availability of Security Group in SigningHub Web

System Behaviour

Yes, the security group exists.

Yes, the mapping for the security group exists.
  • In case the user was already registered, the system will log in the user as per the assigned role.
  • In case the user was not already registered, the system will register, auto activate, and log in the user as per the assigned role.

Yes, the security group exists.

No, the mapping for the security group does not exist.
  • In case the user was already registered, the system will log in the user as per the default role.
  • In case the user was not already registered, the system will register, auto activate, and log in the user as per the default role.

No, the security group does not exist.

N/A
  • The system will throw an error and will not allow auto-provisioning.



See Also