Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
System
4 years agoSuper Contributor
[40] Troubles with biometric unlock (Windows)
This discussion was created from comments split from: CLI 2.0 beta.
Backspaze
4 years agoDedicated Contributor
I've switched to the nightly build now and am running 80500116.
CLI says it's up to date:
op update
1Password command-line tool 2.0.0-beta.11.
You're using the latest version.
This part in the error message is gone now: [ERROR] 2022/01/26 20:49:17 received unexpected response from 1Password app. Please make sure 1Password CLI and the 1Password app are up-to-date. But I'm still getting the null error:
Invoke-Expression : Cannot bind argument to parameter 'Command' because it is null.
At line:1 char:18
+ Invoke-Expression(op signin my)
+ ~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (:) [Invoke-Expression], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.InvokeExpre
ssionCommand
I believe I figured out the reason though. The setting clearly says Biometric Unlock... and I just took for granted that it would work with Windows Hello, no matter if you're using a PIN code, finger print or something else. I don't have any kind of device for biometric auth on my desktop. I use Windows Hello with a PIN, so I guess that's why it's not working. Since the Windows Hello prompt for the PIN code popped when I tried to sign (just as it does when unlocking the 1Password for Windows) I thought that it was working and that some bug stopped it from recognizing that I'd approved the log in with my PIN code.
I'm guessing full support for all the different kinds of Windows Hello options will come in time?