Skip to content

SSH Keys added via Connect cannot be read by 1Password CLI #107

@twbrowning

Description

@twbrowning

Scenario & Reproduction Steps

  1. manually create SSH key in 1Password desktop

  2. get json for that item:

$ op item get "example ssh key" --format json
  1. remove the ID from the json and change its title, then use connect to create an identical item using this json

  2. try to read back the item you just created using op:

$ op item get "example ssh key 2" --format json
[ERROR] 2025/10/27 09:54:28 "private_key" isn't a field in the "example ssh key 2" item

Actual Behavior

Also of note is that the resulting SSH key created by connect doesn't correctly conceal the private key field, nor give it the usual password quality indicator that you do get if you create the record in 1Password desktop.

I haven't been able to find a valid syntax for creating a key. Via op we can ask 1Password to generate it by just passing no parameters; but doing the equivalent with connect results in a key item with no data on it.

Expected Behavior

No response

SDK version

1.5.3

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions