Unable to create a token from the CLI even with proper access to the vault

[arunsathiya]

Hi there! I am a new 1Password Connect user. Following the documentation on this GitHub README, I created a Connect Server (not deployed yet at this point) but creating a Token fails with the error: Couldn't issue the token: "can't grant access to the vault: You do not have the requested access to vault

➜  ~ op connect server create Connect --vaults redacted
File /Users/arun/1password-credentials.json already exists, overwrite it? [Y/n]
Set up a Connect server.
UUID: redacted
Credentials file: /Users/arun/1password-credentials.json
➜  ~ op connect token create Test --server Connect --vaults redacted
[ERROR] 2023/02/14 00:05:08 Couldn't issue the token: "can't grant access to the vault: You do not have the requested access to vault 'Temp'."

If it matters, even after deploying the Connect server on my infrastructure (a Docker container in my MacBook), token creation fails.

Any insights on why this is happening would be great, thank you!

[mtiller]

I'm running into the same issue. Did you ever figure out what was going on?

[mtiller]

FYI, my workaround for this was to do this all through the web pages. I couldn't get the CLI to do it, but via the web application I was able to create a token with the proper permissions without it complaining that I didn't have the permissions needed to create such a token. Then it was some work to go back and update the onepassword-token Secret in Kubernetes, but it all seems to be working now.

[jillianwilson]

Hi there, thank you for raising this. We have done some investigating and think we have found the issue. We hope to release this fix soon. We'll be sure to update this issue once the fix has been released.

[ingvarch]

Passed 1 year. Any updates?