When I was testing the new RC version (before the release) I noticed that my previous Invoke-Expression call to op signin no longer worked. And each call to op resulted in a biometric prompt. It looks like the new 2.3.0 client on Windows isn't idempotent, and if you want to keep the original flow, you need to set $env:OP_BIOMETRIC_UNLOCK_ENABLED = $false.
It's definitely not a problem with the module, but I suspect folks will run into this. This may merit a call out in the readme?
When I was testing the new RC version (before the release) I noticed that my previous
Invoke-Expressioncall toop signinno longer worked. And each call toopresulted in a biometric prompt. It looks like the new 2.3.0 client on Windows isn't idempotent, and if you want to keep the original flow, you need to set$env:OP_BIOMETRIC_UNLOCK_ENABLED = $false.It's definitely not a problem with the module, but I suspect folks will run into this. This may merit a call out in the readme?
https://1password.community/discussion/148560/op-signin-not-idempotent-windows