[CLI2] `whoami` command with `--session` and `--account` errors out and ignores `--session`

vitorqb

Hi there!

I was using something like this to check whether a session was still valid for a specific account:

op whoami --session $SESSION --account $ACCOUNT
if [ $? = 0 ]
then 
  echo "Still valid"
else
  echo "Not valid"
fi

I could swear this worked at some point, but now all I see is this error:

[ERROR] 2022/06/24 12:22:51 could not find session token for account $ACCOUNT

The whoami commands only seems to be working if I login using

eval $(op signin)

Once I do this, then the op whoami command above works, but it completely ignores the --session parameter:

$ op whoami --session foo --account $ACCOUNT
Shorthand:    $ACCOUNT
URL:          ...
Email:        ...
User ID:      ...

Could it be that there is a bug on the whoami command which is completely ignoring the --session cli parameter, and exclusively reading the token from the environmental variables?

CLI VERSION: 2.4.1

Thanks!

---

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser:_ Not Provided
Referrer: forum-search:[CLI2] whoami command with --session and --account errors

Horia.Culea_1P

Hi @vitorqb , thank you for notifying us about this!

Indeed, it seems to be a bug, that op whoami ignores the --session flag.
We have opened a ticket in our internal tracker, looking to get this fixed. We'll keep you updated with any developments related to this.

Let us know if you have any more feedback for us!

Best,
Horia

koensandwave

Hello Horia,

I've been debugging my scripts for quite a while but it seem to be a bug within the op whoami command. Do you have any update for this?

Currently this bugs means there is no way to determine if a user is already logged over CLI.