Empty response from `op signin --raw`?

flappy
flappy
Community Member

I haven't used CLI before so I'm not sure if I'm doing something wrong, but I suppose op signing --raw should output the token in command line? Running op signin --raw --debug in cmd.exe:

4:20AM | DEBUG | Session delegation enabled
4:20AM | DEBUG | NM request: NmRequestAccounts
4:20AM | DEBUG | NM response: Success
4:20AM | DEBUG | NM request: NmRequestAccounts
4:20AM | DEBUG | NM response: Success
4:20AM | DEBUG | NM request: NmRequestAuthorization
4:20AM | DEBUG | NM response: Success
4:20AM | DEBUG | NM request: NmRequestAccounts
4:20AM | DEBUG | NM response: Success
4:20AM | DEBUG | NM request: NmRequestDelegatedSession
4:20AM | DEBUG | NM response: Success

So seems like everything succeeded but nothing got returned?


1Password Version: 8.10.3
Extension Version: 2.16.1
OS Version: Windows 11
Browser:_ Not Provided

Comments

  • flappy
    flappy
    Community Member

    Anybody able to answer this?

  • sandstrom
    sandstrom
    Community Member

    Does it work if you unclick "Connect with 1Password CLI" under Settings -> Developer?

    ( I had that problem with 1Password 8).

  • jtsoi
    jtsoi
    Community Member

    Yes, having the same issue on 1Passworc v8.x

    Seems like CLI <> Desktop app integration is buggy.

    Workaround by disabling "CLI integration" in developer setting in the Desktop App.

    1Password team, this looks like a bug.

  • Thank you for raising this with us!

    This is rather an issue in the help-text: with the OP8<>CLI integration enabled, the CLI delegates its session management to 1Password 8. The --raw option of op signin would only work with normal CLI sessions, reason why it's not outputting anything, when the connection between the two apps is on.

    I'll file an issue to clear this out in the documentation, thank you once again for bringing this to our attention.

    Best,
    Horia

This discussion has been closed.