Android phones

Owned by Lars Olav Velle (Unlicensed)
Last updated: Jun 16, 2020 by Eirik Bjørsnøs
2 min read

Overview

This article shows how two-factor enrolment works for users logging in from Chrome on Android. 

The examples shown here assume that an administrator has already added a multifactor policy which requires that users enrol in extra verification. The details on how policies may be configured is out of scope for this article.

Enrolment

When an Android user is required to enrol in extra verification, they will see a screen informing them that enrolment is required:

The user selects to set up extra verification using Android lock screen. Users who have not enrolled a fingerprint will be asked to verify by entering their Android lock screen PIN.


Naming the registration

After registering the phone, the user is asked to give their registration a name. This makes it easier to remember which device was registered in the future.

Use case summary

The final step in the registration process lists the different ways the user may use the Android device as an additional verification factor:

Once this step is completed, the enrolment of the extra verification factor is complete, and the user can get back to work.

See it in action

See how enrolment works from an end user perspective using an Android device.

Next steps