Introduction
Ensuring secure storage, tokenisation, and verification of Aadhaar data is essential for organisations that follow compliance guidelines and data-protection standards.
uKnowva HRMS supports this process through the Aadhaar Vault extension, which allows administrators to safely manage Aadhaar numbers with encryption and tokenization features.
This article provides a detailed, step-by-step guide to help you configure the Aadhaar Vault settings within your uKnowva instance so your organisation can manage Aadhaar-related processes in a secure and compliant manner.
Step 1: Ensure the Aadhaar Vault Extension Is Installed
Before starting the configuration, make sure that the Aadhaar Vault extension is installed on your uKnowva HRMS instance.
Visit the Aadhaar Vault extension on the uKnowva Extension Store to learn more and initiate installation; a pricing call is required as it involves commercial terms.
Once the installation is complete, you can proceed with configuring the plugin to enable secure Aadhaar tokenisation and de-tokenisation functionalities.
Step 2: Navigate to the Aadhaar Vault Configuration Settings
To configure the plugin, log in to your uKnowva HRMS instance and click on your profile icon at the top-right corner of the page.
When the drop-down menu appears, select the uKnowva Configuration option.
This will open a new interface containing various system settings. From the list of side menus, click on the Plugin Manager to view all the plugins installed in your instance.
You can either scroll through the list manually or use the search bar to quickly locate the Aadhaar Vault plugin.
Once you find it, click on the plugin name to access the configuration.
Step 3: Configure the Aadhaar Vault Plugin Details
When the configuration pop-up opens, you can now enter the details required for enabling Aadhaar tokenisation and secure data handling.
The system provides several fields that must be filled in accurately to ensure that the plugin communicates correctly with the Aadhaar Vault service.
These fields include the Authentication Endpoint, Tokenisation Endpoint, and Detokenization Endpoint, which define how your HRMS instance connects to the Aadhaar Vault server.
You must also enter the API Key, Secret Key, API Username, and API Password to authenticate your organisation’s Aadhaar-related requests securely.
Additional fields, such as Transaction Prefix and Request Timeout (seconds), help customise how requests are processed.
You can also select the Aadhaar Number Field to define where Aadhaar numbers will be stored within the employee profile.
The configuration also allows you to specify which users are permitted to Perform Import and Export operations.
Finally, the Detokenize Bearer Token field enables secure retrieval of original Aadhaar numbers whenever needed.
Once all required fields are completed and verified, click on the Save button to apply the changes. If you prefer not to proceed, click on Cancel to discard any updates.
It is important to note that the Aadhaar Vault team will also have a dependency at the final stage.
Your organisation’s portal URL must be whitelisted by the Aadhaar Vault team in order for API requests to function correctly.
Ensure you coordinate with the Aadhaar Vault service provider to complete this final step.
Conclusion
That’s it!
You’ve now successfully configured the Aadhaar Vault extension in uKnowva HRMS.
By following this process, you ensure that your organisation manages Aadhaar data securely using tokenization, encrypted endpoints, and role-based access.
If you have any questions or need additional support, feel free to contact us at This email address is being protected from spambots. You need JavaScript enabled to view it..