[40] Troubles with biometric unlock (Windows)

Happy to help, Backspaze !

@"Justin.Yoon_1P"

Aha! So it was the Invoke-Expression that was the culprit. I tried with op signin now and it worked flawlessly. Thanks for clearing that up!

Hey Backspaze

While I am not currently able to answer whether or not Windows Hello with PIN works with Biometric Unlock, so I've reached out to my colleagues to get an answer on that.

For the time being, I wanted to let you know that when biometric unlock is enabled, the op signin command no longer needs to be wrapped in Invoke-Expression, that's because system wide authentication works differently than CLI standalone authentication.

Alternatively, you can try executing any command (many people tend to use op user list for some reason..) to invoke the biometric unlock process instead of explicitly running the op signin command as well.

Hope this helps for now, and we'll get back to you regarding the first part of your question.

Edit: Just heard back from a colleague within minutes, so I'll edit my post instead of making a new one.

Looks like Windows Hello PIN should work for unlocking the CLI, in fact we have some developers who use the Hello PIN in-house.

So for now, do you mind leaving out the Invoke-Expression a try and get back to us here if the issue persists?

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?

Hey Backspaze 👋 I saw your thread and added you to the private forum group here for the beta. Before I send this over to the team, I just want to make sure that you're running the Nightly version of 1Password 8 for Windows? To select the Nightly channel, you need to open https://1password.com/downloads/windows/, click the account or collection at the top of the sidebar and choose Settings > Advanced, then select Nightly for the release channel. Then click on About > Check for Updates. Make sure the build is 80500112 or later.

Just checking in here about the CLI 2.0 beta. I'm using the beta of the Windows desktop app and today I got version 8.5.0-103 installed and found that you'd added a setting for integrating with 1Password CLI. Naturally I began poking around for getting my hands on CLI 2.0 and found https://developer.1password.com/ as well as the https://app-updates.agilebits.com/product_history/CLI2 where I could download it. I ran into an error with the integration with the desktop app when trying to sign in to CLI 2.0. It triggered the Windows Hello prompt but returned the error Invoke-Expression : Cannot bind argument to parameter 'Command' because it is null.. Without the integration with the desktop app, it asks for for my account password and I can sign in just fine.

I figured I should report this and headed to this forum as usual but couldn't find a category for the beta of CLI 2.0. As the documentation I linked to above is public and anyone can download the beta from the change log page I thought there would be a forum category ready. But according to this thread you'll have to be invited either by asking here in this thread or by filling in https://bit.ly/1P21BetaDocs (which also is referenced in the documentation).

So, I guess I should stop writing short novels here and fill out the form and see if I'll get access...?

EDIT: I've filled out the form but for the sake of completeness, I'll just leave the full error message below in case I don't get access to the forum.


[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.
Invoke-Expression : Cannot bind argument to parameter 'Command' because it is null.
At line:1 char:19
+ Invoke-Expression (op signin my)
+ ~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (:) [Invoke-Expression], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.InvokeExpre
ssionCommand