User Flow - 4. Logging in with a Silent MFA user who has an existing MFA device

This case is where a registered user with their usual device logs in to customer application. In this case, both the user and their device are known to Haventec Silent MFA. Therefore, Haventec Authenticate login API is successfully called right away.

As Silent MFA SDK found credentials in the user’s device, it automatically logs in using these credentials. This case is where the seamlessness shines. Even if the user logs in to customer application a thousand times a day, there will be no added activity on the user’s part while they are enjoying the additional security of the added factor in the authentication process which is Haventec Silent MFA.

The above flow goes as follows.

1. The end user logs in as usual to the customer frontend. 

2. The customer front end calls the SDK login service with a username and password.

3. The SDK FrontEnd retrieves Haventec authKey, userId and token from the user’s local storage. (This scenario is the ideal case where the credentials are already saved in local storage).

4. The SDK FrontEnd calls POST /login of customer Backend with relevant login details.

5. Then the customer BackEnd executes POST /authentication/login Login MFA Device with the appropriate applicationId, apiKey, authKey and deviceId.

6. The login was successful and a new set of authKey and token is returned.

7. The customer BackEnd sends the new authKey and token back to the SDK.

8. The SDK saves the fresh credentials in the user’s local storage.

9. The success is returned.

10. The login is successful with the new authKey and token ready to be used for the next login.