"op signin" prompts even when a session is still valid

Hi,

I'm developing a little script that our CSMs use. The script connects to DB, runs some queries, and produce output for them. I'd like to use 1Password to store the credential to connect to DB. That way, the only prompting that CSM ever gets is their own 1Password, which is much easier for them. I'm feeling this is a fairly standard use case for the op CLI.

The problem I'm having is that when I run op signin , it always prompts the user to establish a new session token. This is cumbersome. The behaviour I'd like is that the prompting only happens when there's no valid session at the moment. saml2aws, which is a similiar tool for different services, work exactly like this.

I eventually discovered that eval $(op signin --session "$OP_SESSION_foobar" foobar) seems to do the trick, but I find this rather unintuitive for a seemingly common use case like this. It makes a lot more sense to me that the default behaviour consults the existing session token, and for the rare situation where you want to force reauthentication, define --force or something.

Just my 2 cents.


1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided

Comments

  • ag_Aprilag_April

    Team Member

    Hello @Kohsuke,

    I'm glad you were able to find a solution for your use case, and I'm sorry that it wasn't as intuitive as it could have been. We really appreciate your feedback, and I've shared it with the rest of the team so that we can consider this when planning future updates.

    Please feel free to reach out any time with additional feedback or questions.

    Thanks,

    April

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Emoji
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file