Allow Touch ID When Switching Between Apps

burnum

Pre-Reqs:
Use Touch ID to unlock 1P Vault.
Enable Lock on Exit

Issue 1: Double Press of Home Button does not activate app switcher when asking for Touch ID from 1P.

Steps to Reproduce:
1) Launch 1P so it's prompting you for Touch ID to unlock vault.
2) Double press home button

Expected Result:
Brings up app switcher

Actual result:
Opens 1P vault

Issue 2: User prompted for master password (not touch ID) if Touch ID had been canceled in a previous session.

Steps to Reproduce:
1) Launch 1P so it's prompting you for Touch ID to unlock vault.
2) Single press home button (Touch ID will cancel, 1P will prompt for master password)
3) Double press home button (App switcher will activate)
4) Switch to another app
5) Switch back to 1P

Expect Result:
Prompted for touch ID

Actual Result:
Prompted for Master Password

Notes:
I frequently find myself looking at the 1P Touch ID prompt when waking up my phone (I forgot to close 1P). I'll instinctively use the home button to switch to another app. Then later when I need to log into 1P, it won't prompt me for Touch ID because I accidently dismissed Touch ID earlier when switching apps. I've started to try to train myself to only switch out of 1P when I've logged in to the vault so not to accidentally cancel Touch ID (I have a rather long master password).

I understand there are certain times when the master password is required, but if the user dismissed Touch ID, I think the app should offer Touch ID again when switching back into 1P from another app (so it should reset the prompt state).

For example, Authy does a good job of managing Touch ID vs App Switching vs asking for a PIN.

---

1Password Version: 6.2.2
Extension Version: N/A
OS Version: iOS 9.2.1 (iPhone 6S)
Sync Type: N/A

Ben

Hi @burnum,

Thanks for taking the time to write in, and for the detailed report on this difficulty. Unfortunately I think most of the problem here stems from the fact that the home button is also the Touch ID sensor, and all interaction with that is handled by iOS itself (not 1Password). We simply send a call to iOS to authenticate with Touch ID. The actual Touch ID prompt and any input processing is done by iOS, and then they return to us what is essentially a "yes" or "no."

I'll certainly pass the feedback along to our developers to see if there are improvements that we can make in this area, but my (limited) understanding is that much of this is iOS behavior, not 1Password behavior.

Thanks!

Ben

burnum

Thanks Ben for the reply. I get what you are saying, but hope there's a work around. I'd just point out to take a look at the Authy app, because they've figured out how to handle this a little better IMO. Best, Steve

dszp

I do believe there are users here that rely on the process you mention in Issue 2 as well. If they wish for the master password to be required rather than allowing Touch ID, canceling Touch ID (which pressing Home appears to do, in addition to the on-screen Cancel button) will always require the master password next time to unlock the vault. This would prevent anyone from forcing the use of a fingerprint to unlock the vault until the master password was known/used.

This could be used to prevent kids from unlocking your vault with your finger while you sleep, or to prevent Customs from forcing you to unlock your vault with your finger vs a password only in your head, depending on your security needs :-)

Ben

It is certainly worth further investigation. :)

Ben

burnum

In a recent update, I see there's now an icon to select TouchID auth below the password field prompt. That made me really happy.

nmott

@burnum it certainly comes in handy if you have to cancel the dialog (like when you want to access the app switcher, as described above) but then want to use Touch ID when you head back to 1Password :)