Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
We want your feedback on biometric unlock!
I've said this a few times already but I just want to reiterate how thankful we are that everyone here is testing out CLI 2.0 and giving us such amazing feedback. As a reminder, we will be giving out some pretty awesome prizes soon so keep your eyes peeled to the forum for an announcement on that.
In the meantime, I'd love to hear your thoughts and opinions on how our new biometric unlock feature for CLI 2.0 is working for you. We've seen a few threads so far but we'd love to hear if you're running into any issues or just want to rave about how cool it is and how it has impacted you! Our goal is to continually make your workflows more streamlined and more secure so if there's anything you want to share about biometric unlock for how it's working for you (or not working for you) please reply in this thread!
We can't wait to hear from you.
15 Replies
Oh no, you broke biometric unlock in 1Password 80600017 (Nightly):
|[ERROR] 2022/02/13 14:51:17 could not read secret op://vault/item/username: error initializing client: biometrics currently not available. Please open 1Password, unlock it with your password and then try again
:cry:
Note: 1Password is already opened and unlocked...
Please hurry fixing this; the 1Password experience is so much better when this feature works!
I've been using it for the past few days and it's been a huge QoL improvement for me. Since biometric unlock was introduced, I've integrated 1password CLI v2 into a lot more scripts. I was pleasantly surprised by how seamless it was to use.
There are some tools I use that stored secrets in plaintext in the home directory. With the reduced friction since biometric unlock was introduced alongside the inject command/templating config, I've been able to generate these configurations on demand. Definitely feels like my system is more secure now. It's also allowed me to commit environment and config files confidently without worrying about leaking credentials!
One minor piece of feedback: I use multiple panes and windows in my terminal, so it would be great if the Biometric unlock didn't show an allow prompt for each of them. It's not a big deal and I figured there's probably a good reason for why it does - but thought I'd share it either way :)
@rknshia & XIII, you have no idea how big of a smile you put on my face this morning reading your feedback. I've passed that directly along to the development team as they worked incredibly hard creating this feature.
If anyone else has feedback they'd love to share please don't hesitate to share here in this thread. We love hearing positive feedback but also want to hear about anything that's not working optimally for you.
And thank you again for taking the time to beta test CLI 2.0!
Biometric unlock is flawless here!
In fact, it's the reason I started using the CLI at all... 1Password CLI 1.0 that was just not a fit for my needs (because I would have to type my master password in a shell when using it). I have completely redefined a few Keyboard Maestro macros that help me log in outside of the browser. Previously they used the GUI (Quick Access) which worked most of the time, but it was pretty annoying whenever they did not. I use the CLI based versions (multiple times each day) since I learned about biometric unlock and they work flawless ever since. I enjoy using them every time!
