CLI signout completely broken

jscarle

The op signout command of the CLI is completely broken. It is impossible to sign out of an account, you must wait for the token to expire. While the token is still valid, the op signout command does nothing and it is consequently impossible to use the op account forget command. Using the --forget flag on the op signout command also does nothing.

Repro steps
1) Add an account using op account add.
2) Sign in to this account using op signin.
3) Attempt to sign out and forget the account by using op signout, then op account forget [account]. It will say that you are currently logged in.
4) Attempt to sign out and forget the account by using op signout --account [account] --forget, then use op account forget [account]. It will say that you are currently logged in. Account can be confirmed as still remembered by using op account list.

Workarounds
As it stands, the only two workarounds are 1) by going to website and forgetting the device there, therefore forcing a sign out the next time the CLI runs, or 2) using op signout --all, which effectively forces a sign out of all accounts, which is proven by the fact that the op account forget [account] command then works correctly and the account is no longer listed by the op account list command.

Additional notes
This is a longstanding issue as it has been mentioned in various forms here:

• https://1password.community/discussion/119973/can-not-signout-account
• https://1password.community/discussion/125637/op-signout-does-not-work
• https://1password.community/discussion/112562/signout-forget-leaves-sensitiv-data-behind
• https://1password.community/discussion/113898/op-forget-and-op-signout-forget-dont-seem-to-actually-forget
• https://1password.community/discussion/comment/389320#Comment_389320

---

Tested using 1Password CLI Version: 2.6.2

jscarle

Consequently, the op whoami command doesn't work, which is probably tied to the same issue as the sign out.

andi.t_1P

Hi @jscarle, I have been trying to reproduce this for a while but to no success. Could you send over the exact sequence of commands that get you the bug? Also are there any particularities which go with running this command, such as what state is you app in? Do you have any other accounts added to the cli? If yes, how many?

All the best,
Andi