SigningHub gives you an option to pre-authorize users in your Azure 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 won't even need to create their SigningHub IDs.
Configure an Azure Active Directory connector in SigningHub Admin.
Configure the connector in an authentication profile, in SigningHub Admin.
Configure auto provisioning in SigningHub Web.
Configure a security group for auto-provisioning.
Auto-provision the users at login
Make the following configurations to a connector in SigningHub Admin:
In the "Basic Information" section, choose "Azure Active Directory" as the "Provider".
In the "Details" section, fill in the required fields.
In addition to "User.Read", an additional mandatory permission, "Directory.Read.All", will have to be configured for pre-authorization of users in Azure Active Directory.
Make the following configurations to an authentication profile in SigningHub Admin:
Select the Azure Active Directory Connector created earlier, in the highlighted field below:
If you want to allow access to specific authorised security groups in your Azure 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.
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.
To see in detail, how to pre-authorise users in SigningHub, click here.
Make the following configurations in the "Users" tab in SigningHub Web:
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.
All the users that belong to the selected authentication profile will be authorised through Azure 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.
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.
Both public and private authentication profiles will be visible in the "Authentication Profile" drop-down for pre-authorising users.
SingingHub also allows you to give role-based access to SigningHub (i.e. Enterprise Admin, Enterprise Users, etc.) at the Security Group level.
Make the following configurations to a security group in SigningHub Web:
For the security group, add the name and role of the security group.
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.
The names of the security groups are not validated against the security groups in the Azure Active Directory, at this screen, so the correct security group name must be added for successful pre-authorisation upon login.
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.
Logging in through your Azure Active Directory credentials for the first time, will take you to the registration screen and display your Azure Active Directory (email address) for new registration. After registration, you can easily login through your Azure Active Directory credentials. However, if the "Automatically register the users" check box is ticked from the "Auto Provision Users" screen, and an Azure Active Directory has been selected as an Authentication Profile, then the registration screen will not be displayed, as the provisioned Azure Active Directory users from there will be automatically registered and activated in SigningHub.
From the "More Login Options" option, select Azure Active Directory.
Provide your Azure Active Directory credentials.
The following login preferences will be followed when logging into SigningHub Web via Azure Active Directory:
SigningHub gives you an option to use your Microsoft Azure Active Directory credentials to log into SigningHub. In this case, you don't even need to have a SigningHub ID, as your account will be used for SigningHub authentication. However, logging in through your Azure Active Directory credentials for the first time, will take you to the registration screen and display your Azure Active Directory (email address) for new registration. After registration, you can easily log in through your Azure Active Directory credentials.
However, if the "" is enabled from the "Auto Provision Users" screen, and an Azure Active Directory has been selected as an Authentication Profile, then the registration screen will not be displayed, as the provisioned Azure Active Directory users from there will be automatically registered and activated in SigningHub.
Go to the SigningHub login screen.
Click the "More Login Options" link available at the bottom of the login screen. A dialogue box will appear listing all the supported authentication methods.
Click the "Azure AD" option. The Microsoft Azure Active Directory app will appear in a popup.
Specify your Microsoft Azure Active Directory ID and password in the app.
Click the "Sign in" button. You will be authenticated into SigningHub.
In order to make your Azure Active Directory application running, you need to manually update a property on the Azure Portal under the application's manifest.
For this:
Click Manifest at the left pane describing your app.
Change the value of the oauth2AllowImplicitFlow property to True. If the property is not present, add it and set its value to true.
Click "Save" to save the modified manifest.
In order to make your Azure Active Directory application run, you need to manually update a property on the Azure Portal under the application's manifest.
For this:
Click Manifest at the left pane describing your app.
Change the value of the oauth2AllowImplicitFlow property to True. If the property is not present, add it and set its value to true.
Click "Save" to save the modified manifest.
As a part of GDPR compliance, the "Service Agreement" dialogue box will appear after successful user authentication. This dialogue box contains the links to the "Terms of Service" and "Privacy Policy" pages. SigningHub will ensure that you agree to them before letting you use your account.
The "Service Agreement" dialogue box will not appear after successful user authentication if no Service Agreement is marked active.
When using an on-premises installation of SigningHub and this is the only configured authentication for the end-users, then you won't need to click the "More Login Options" link to choose it. In that case, this authentication method will be invoked by default on the Login screen.
Users cannot log in to SigningHub if their account is disabled, marked as dormant, or temporarily locked due to multiple invalid login attempts.
| Availability of Security Group in Azure 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.
