Injecting secrets with op command does not work with Work Organization account
I am experiencing the same issue as discussed on this closed thread:
I am using op version 2.30.0
I get the account USER ID from the op accounts list
and whether I use the --account
flag or the OP_ACCOUNT
env variable I see the same result:
❯ op accounts list URL EMAIL USER ID workorg.1password.com workemail@example.com YFHU••••••••••••••YJA my.1password.com personalemail@gmail.com 6LZDD••••••••••••KWA ❯ export OP_ACCOUNT=YFHU•••••••••••••••••YJA ❯ op run --env-file=.env --no-masking -- printenv API_TOKEN [ERROR] 2024/09/26 14:58:35 "Personal" isn't a vault in this account. Specify the vault with its ID or name.
The Work account does not have a Personal vault, it has an Employee vault instead. As well the vault is specified in my op:// URI so I am not sure why it even attempts to access a "Personal" vault.
Example op URI: op://Customers/TestScript/API_TOKEN
where Customers
is the Vault name, TestScript
is the Item name and API_TOKEN
is the field name.
If I specify a URI for my personal 1password account everything works as expected.
Any help would be appreciated!
1Password Version: 8.10.44 (81044034)
Extension Version: Not Provided
OS Version: macOS 14.6.1
Browser: Not Provided