Skip to main content
XIII
February 15, 2022
Question

[2033] CLI 2 bio-metric unlock broken after enabling SSH beta feature

  • February 15, 2022
  • 12 replies
  • 171 views

After enabling the SSH beta feature I can no longer use CLI 2's biometric unlock (I have to type my password again).

Are these features currently mutually exclusive? :(

(PS: Not sure in which of the two forum sections to post this...)


1Password Version: 80600027 Nightly
Extension Version: n/a
OS Version: macOS Big Sur 11.6.4

12 replies

February 16, 2022

+1. I'm also facing the same issue after enabling the SSH beta.

February 16, 2022

Thanks for reporting this folks! I've alerted our engineering team and we're going to look into this ASAP.

1Password Employee
February 16, 2022

Thank you for reporting this! We'll look into the issue. The two features should not be mutually exclusive.

floris_1P
1Password Employee
February 16, 2022

@XIII @smanojkarthick On which CLI beta version are you? And what does your terminal output say?

February 16, 2022

I'm on CLI version 2.0.0-beta.12 and App version: 8.6.0 80600028.

This is the error message:

❯ op read op://path/to/secret
[ERROR] 2022/02/16 04:20:06 could not read secret op://path/to/secret: error initializing client: You are not currently signed in. Please run `op signin --help` for instruction

XIII
XIIIAuthor
February 16, 2022


➜ op --version
2.0.0-beta.12

and

``
➜ op item get ...
[ERROR] 2022/02/16 13:21:34 error initializing client: You are not currently signed in. Please run
op signin --help` for instructions

➜ op signin
Enter the password for user@domain.com at domain.1password.com:
```

1Password Employee
February 16, 2022

Hi both, we believe we have found the problem and a way to get it working again.

Running the following should solve the problem:

For macOS:
chmod 600 ~/Library/Group\ Containers/2BUA8C4S2C.com.1password/Library/Application\ Support/1Password/Data/settings/settings.json

For Linux:
chmod 600 ~/.config/1Password/settings/settings.json

Thanks again for reporting the issue and please let us know if the solution works for you.

February 16, 2022

Thanks a lot @1P_Simon ! That fixed it for me on macOS.

1Password Employee
February 16, 2022

Awesome! Thanks for confirming

XIII
XIIIAuthor
February 16, 2022

Yes, that works for me too (macOS)! Thanks!

In case it matters: I modified that JSON file using the jq command in the documentation (so not manually).