Signing back into the Community for the first time? You'll need to reset your password to access your account.  Find out more.

Forum Discussion

zcutlip's avatar
zcutlip
Dedicated Contributor
3 years ago

Feature request: headless/non-interactive mode

It would be nice if op had a flag that would suppress any interactive prompts. So instead of prompting for things like password, biometric auth, or adding an account, you would get a hard failure. ...
CLI
zcutlip's avatar
zcutlip
Dedicated Contributor
3 years ago

I'm sorry; I wasn't very clear.

Let's take this scenario:

  • I think (or, more accurately my script thinks) I'm signed in already because I've done one of the following
    • previously run op signin
    • set OP_SESSION_<user_id> to what I believe is a valid session token
    • set OP_SERVICE_ACCOUNT_TOKEN to what I believe is a valid service account token
  • BUT I'm actually not authenticated because one of the following
    • the session has expired, or
    • the service account has been revoked, or
    • some other mistake
  • In some cases, an op item get operation (or similar) will prompt via GUI or command line to sign in before proceeding
    • This prompt for user interaction will hang forever if there's no user, so I need to avoid it, and just log an error

What I'd like is a mode to guarantee an op item get or any other operation is a hard failure if we're not authenticated (or our authentication has expired or been revoked), rather than be prompted to re-authenticate

Does that make more sense?