Transcript
Requiring a code from an authenticator app for sensitive roles, setting it up, signing in with a code, and recovery codes.
0:00 Introduction
A password can be guessed, or stolen. Two-factor sign-in adds a second step: a six digit code from an app on your phone. In this episode we see how that works for your staff, from the first sign-in to the day someone loses their phone.
0:15 Why and who
The code comes from an authenticator app, which makes a new code every thirty seconds. Without the phone, a stolen password is not enough to get in.
You decide who must use it. In the store settings, your administrator lists the permissions that need two-factor. Here, voiding a sale is one of them. Anyone whose role includes a listed permission must set up two-factor before they can do anything else.
0:41 The first sign-in
Taylor is a manager, and the manager role can void sales. Taylor signs in with an email and a password, the way they always have.
Instead of the dashboard, Taylor lands on the profile page. It says that their role requires two-factor sign-in, and offers a button to set it up. Until Taylor does, the back office does nothing else.
1:03 Setting it up
Taylor taps Set up two-factor sign-in.
The page shows a QR code. Taylor opens an authenticator app on the phone, and scans it. If scanning is not possible, the app can also be given the key that is printed underneath, by typing it in.
The app now shows a six digit code for this store. Taylor types it into the Code box, and taps Turn on.
1:27 Recovery codes
Two-factor is now on. The page shows ten recovery codes, once only. Each one works one time, in place of the code from the app.
If the phone is lost, broken, or replaced, a recovery code is the way back in. Taylor should save them somewhere safe, such as a password manager, or print them. Then tap, I have saved them.
The codes are gone from the screen, and the profile page is ready.
1:54 Signing in with a code
From now on, signing in has two steps. Taylor signs out, and signs in again with the email and the password.
Now the back office asks for a code. A wrong code is refused, and the person stays on this step. And a code can be used only once, so Taylor waits for the app to make a new one.
Taylor types the current code from the app, and taps Verify. Taylor is in.
2:20 Lost your phone
Now suppose that the phone is gone. Taylor signs in with the password again.
At the code step, Taylor types one of the recovery codes instead of the code from the app.
It works, once. That recovery code is used up, and nine remain. The use of a recovery code is recorded in the audit journal. Taylor should now set up the authenticator app on the new phone.
The profile page has a Turn off button. But while Taylor's role requires two-factor, the system refuses it. Only when the administrator removes the requirement can Taylor turn two-factor off.
That is two-factor sign-in. In the next episode, we move to the register, and look at PINs, locking the register, and approvals.