Multi-Factor Authentication using Metadata

The Ushur platform employs Multi-Factor Authentication (MFA) for the Invisible App to ensure that only the intended end-user engages with IA, validating through a One-Time Password (OTP). Enterprises can confirm the intended end-users by validating specific user-related metadata in each workflow launched.

The Invisible App's Multi-Factor Authentication (IA MFA) internally relies on the 'Templates' feature.

To implement Multi-Factor Authentication via metadata, modify the template according to the specific requirements of the business case:

1. Import the MFA template from Templates > Search > mfa > Import.

2. Update the mfa workflow with metadata to be queried and validated.

3. Enable MFA for Invisible App for workflow where the authentication is required. To enable multifactor authentication in Invisible App, follow the below steps:

   

   1. Go to SETTINGS.

   2. Under the Verification section, Select the checkbox to enable MFA for Invisible App.

Note

The MFA feature applies to all the workflows in the Enterprise Account where IA Setting > Enable MFA for Invisible App is enabled.

Business Case – MFA via Date of Birth

Follow the below-mentioned step to create multi-factor authentication using date of birth:

1. Import the mfa Ushur to the Main application context.

   

2. Open the mfa workflow.

   

3. In the current workflow, the getCode module initiates OTP-based MFA Authentication.

4. Disconnect the getCode module and add the Fetch module to retrieve the user details from your workflow that has metadata.

5. Add the Open Response module to allow the user to enter the date of birth and save it in a Ushur Variable.

6. Add the Compare module to compare the users' entered date of birth (Ushur variable) with the date of birth from the metadata file.

7. If the user enters the correct date of birth, the MFA Ushur will go to the actual workflow. Entering the Jump details are not required.

Note

Keep the process in a loop to handle the end of the workflow as MFA does not have a built-in feature for processing the end.

Limitations

When the MFA template is modified, all workflows with MFA authentication enabled will adopt the updated authentication metadata, making the OTP authentication ineffective.