Cloud DSC

Cloud DSC

Introduction


Cloud DSC is a way to apply IT Act compliant digital signatures, without having to possess a physical token that is necessary in traditional DSC based signing.  Users can simply complete a 100% online, one-time verification process, following which they can access their DSC from any computing device using a PIN and OTP.  


The one-time account creation and verification process takes 30 minutes on average, and can be completed using a PAN card (Reference Video (Creating Signer ID) | Reference Article) or an Aadhaar XML (Reference video - Creating Aadhaar XML | Reference Video (Creating Signer ID) | Reference Article) .


The verification process is completed through a third party called an eSign Service Provider (eMudhra) which is an entity directly regulated by the Controller of Certifying Authorities. 

How to activate


Account settings >> Department >> eSignature


  1. Activate the Cloud DSC toggle

    You can also set this as a default eSign type by activating the Default toggle

    Note: Only one eSign type can be marked as default.

  2. Configure Cloud DSC verification settings


Saving SignerID in the Account 


A Leegality user can also save their eMudhra for repeated use in the New Document flow.


Account Settings >> Settings >> eSignature


  1. Scroll down the “Cound DSC” section and click on setup



  1. To fetch the signer ID enter any 2 of the following:

    1. Signer ID

    2. Mobile Number linked to the SignerID

    3. PAN linked to the SignerID



  1. Click on Validate and Update



Configuring a Cloud DSC Signature - New document Flow


  1. On the invite page - Select the eSignature type as “Cloud DSC”



  1. In the Cloud “DSC Options” side menu, you can:-

    1. Fix SignerID of the invitee

      The signerID is a unique ID created by eMudhra (the Cloud DSC provider) that is used to access the Digital signature certificate of the ID holder.

      This toggle allows the sender to fix the signer id for the invitee and they won't be able to enter a different signerID in the signing journey



To fix the signerID of the invitee, you have to enter any two of the following: 


  1. the SignerID, 

  2. the mobile number linked to the SignerID, and 

  3. the PAN number linked to the SignerID.  


In case this toggle is turned off - the invitee will be asked to either:-

  1. Create a new signer ID, and thereafter enter the signerID in the signing journey

  2. Enter their existing signer ID

  3. Use the signerID saved in the invitee’s account (if any)

  1. Use SignerID saved in your account

As a sender, if you are signing the document yourself, you will also have the option to use the signerID saved in your Leegality account (if any).  





  1. Verify invitee details against certificate details

You can verify the digital signature used to sign the document against the input values specified by you. For Cloud DSC, you can verify the following parameters:


  • Verify Name: verifies the digital signature against the name of the Invitee;

  • Smart Name Verification:  verifies the digital signature against the name of the Invitee with reference to an appropriate percentage threshold as set by you; 

  • Invitee Pin Code: verifies the digital signature against the Pin Code of the Invitee

  • Invitee State: verifies the digital signature against the State of the Invitee

  • Invitee last 4 Aadhaar digits: verifies the digital signature against the last 4 digits of the Aadhaar of the Invitee (note that this works only if the signerID used by the invitee was created using Aadhaar XML)

  • Read more about Certificate verification here: Aadhaar certificate verification



Configuring a Cloud DSC Signature - Workflow

  1. On the invite page - Select the eSignature type as “Cloud DSC”

  2. In the Cloud DSC Options side menu, you can:-

    1. Configure Signer ID of the invitee

      1. If turned off - The invitee will be allowed to enter/ create & enter a signer ID in the signing journey.

      2. If turned on

        1. The user can either enable it (without enforcing) and give the sender option to either configure the signer ID while sending or allow the invitee to enter/create and enter the signer ID in the signing journey

        2. The user can make it mandatory to configure the signer ID in the signing journey

          1. The user can also fix a signer ID that will always be constant for the concerned invitee

            Note: Any 2 of the 3 i.e. Mobile Number/PAN/Signer ID parameters are required to configure the Signed ID automatically



  1. Verify details with the Certificate Details

    You can verify the digital signature used to sign the document against the input values specified by you. For Cloud DSC, you can verify the following parameters:


  • Verify Name: verifies the digital signature against the name of the Invitee;

  • Smart Name Verification:  verifies the digital signature against the name of the Invitee with reference to an appropriate percentage threshold as set by you; 

  • Invitee Pin Code: verifies the digital signature against the Pin Code of the Invitee

  • Invitee State: verifies the digital signature against the State of the Invitee

  • Invitee last 4 Aadhaar digits: verifies the digital signature against the last 4 digits of the Aadhaar of the Invitee (note that this works only if the signerID used by the invitee was created using Aadhaar XML)

  • Read more about Certificate verification here: Aadhaar certificate verification


Sending a document via Workflow


Running a Workflow


Use this Guide to learn more about running a Workflow via the Leegality dashboard - Running a Workflow


  1. In case “Configure Signer ID” is turned off the user can proceed to sending the document

  2. In case”Configure Signer ID” is turned on:-

    1. In case of “Enable” - The user can either configure it or allow the invitee to enter/create and enter the signer ID in the signing journey

    2. In case of “Mandatory” - The user will have to mandatorily configure a Signer ID by entering any 2 of the 3 i.e. Mobile Number/PAN/Signer ID parameters

    3. In case of “Fixed” - The user can proceed with sending the document.

  3. In case Verify details with the Certificate Details has been turned on - The user will have to configure the required parameters for verification against the Cloud DSC.


Sending a document(s) using Excel upload

Use this Guide to learn more about Sending a document(s) using Excel Upload - Running a Workflow - Via Excel Upload


  1. In case “Configure Signer ID is turned off” no additional columns will be provided in the Leegality excel template

  2. 3 additional columns will be provided in the excel i.e. 1.) cloudDSC.signerID 2.)  cloudDSC.PAN 3.) cloudDSC.mobileNumber in case of:

    1. Enable - The user does not have to mandatorily fill the extra columns:

      1. If filled - Only fields are required to be filled and the signer ID will be fetched on the basis of this 

      2. If left empty - The invitee will be allowed to enter / create & enter a signer ID in the signing journey

    2. Mandatory - The user will have to mandatorily input the ⅔ of the cloud DSC columns in order for successful creation of the invite.

    3. Fixed signer ID - The user is not required to fill the cloud DSC columns since the information has already been fixed in the workflow and any information filled here will be overwritten.


Custom Mapping

Use this Guide to learn more about Custom Mapping in the Leegality Dashboard - Custom mapping of workflow spreadsheet template


The 3 additional column headers can be mapped as normal in the Custom mapping module.


Signing Journey


  1. The Invitee will receive a signing link to the document

  2. User reaches the preview page - Clicks on proceed

In case no Signer ID has been provided by the Sender 

The signer is prompted to select on of the following:

  1. Create new Signer ID - Here the user will proceed to an instructions page on how to create a Signer ID on eMudhra:

    1. Creating a signer ID using PAN - Reference Video (Creating Signer ID) | Reference Article

    2. Creating a signer ID using Aadhaar - Reference video - Creating Aadhaar XML | Reference Video (Creating Signer ID) | Reference Article



Once the user has successfully created their signer ID - they will come back to the signing journey and click on proceed and enter their newly created signer ID

Note 1: Successful creation of signerID means the approval of the account by the eSign Service Provider (eMudhra) after video verification. On successful approval, the user will receive an email from eMudhra, with login details for their eMudhra SignerID account. If the user tries to use a signerID for which video verification is not complete, they will receive one of the following errors, depending on the stage of account creation: 


  • “Please enter valid SignerID”

  • “Subscriber steps pending” 

  • “CA Verification pending” 


Note 2: The signer is advised not to close the signing journey tab for a seamless journey, and easy access to the Help resources on the page.  However, even if the signer closes the signing journey page, they can re-click on the signing URL to complete the signing, once their SignerID is ready.

  1. Use an existing Signer ID - The user will be prompted to either

    1. Enter the signer ID
      Or

    2. Fetch the signer ID using their PAN and Mobile Number (this option will work only if a PAN is linked to the SignerID.  In cases where an account is created using Aadhaar XML, linking the PAN to that account is Optional. Users desiring to link their PAN to their eMudhra account can do so here.


Note: In order to use a SignerID it must be a fully verified and active account. If you try to use a signerID for which video verification is not complete, you will receive one of the following errors, depending on the stage of account creation: 


  • “Please enter valid SignerID”

  • “Subscriber steps pending” 

  • “CA Verification pending” 



  1. If the invitee has a SignerID saved in their Leegality account, they will receive an option to use the SignerID saved in their account.


  1. Then click on proceed

In case a signer ID has been provided by the Sender  

After the preview page the signer will be led to the “Confirm Signer ID and Name page



  1. The signer will check the consent box and click on “Sign document



  1. The signer will be redirected to the eMudhra signing page and is required to enter the following:-

    1. PIN - that was set when creating the signer ID (in case you have forgotten the PIN, you can easily reset the PIN by clicking the “Forgot PIN” option.) 

    2. OTP that will be received on their registered mobile number

    3. If the user has set up a time-based OTP (T-OTP) in their eMudhra account, they will be able to proceed by entering the T-OTP. 

    4. Check the consent box


  1. Click on “Perform eSign” button

  2. In case all the details are correctly entered - the document will be successfully signed.




    • Related Articles

    • DSC Token

      A USB token-based DSC (containing the Digital Signature Certificate), can be used by you/counter party for eSigning. You can also use this to sign your documents in Bulk. ​
    • DSC Token - Signing Journey

      Prerequisites for signing via Leegality using a DSC Token:- Leegality DSC Utility should be downloaded and running as administrator: Download link:  ...
    • Procedure for Bulk Sign using a DSC Token

      Download Leegality’s DSC client utility from https://gitlab.leegality.com/leegality-public/dsc-utility. This is a prerequisite to use Leegality’s Bulk Sign feature. Open received folder Click on the Bulk sign button. Note: Only received documents ...
    • NeSL eSign

      How to activate Account settings >> Department >> eSignature To activate NeSL eSign, “NeSL eSign” needs to be enabled.  NeSL eSign can be made the Default signature type using the Default toggle.  NeSL eSign settings can be configured by clicking on ...
    • Received

      This folder shows you all documents for which invitations to ‘eSign’ have been received by you but not signed by you yet. The received folders is where you initiate a BULK signature of upto 500 documents via a DSC Token.