You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When adding an item via the connect API with category = "SSH_KEY", the resultant private_key is continually returned as Field type = "STRING" instead of the passed in Field type = "SSHKEY".
When getting an existing SSH_Key from the Connect API, the response includes the correct Field type = "SSHKEY". I've tested using both Field types of SSH_KEY and SSHKEY as I've seen them both mentioned in the docs/returned responses and connect-sdk-go. I ran into this issue while working on adding SSH Key support to the 1Password Terrafrom provider.
The text was updated successfully, but these errors were encountered:
When adding an item via the connect API with
category = "SSH_KEY"
, the resultantprivate_key
is continually returned as Fieldtype = "STRING"
instead of the passed in Fieldtype = "SSHKEY"
.Example:
item.json
curl -X POST -H "Content-Type: application/json" -H "Authorization: Bearer $OP_API_TOKEN" -d @item.json https://connect-server.example.com/v1/vaults/abc123/items
When getting an existing SSH_Key from the Connect API, the response includes the correct Field
type = "SSHKEY"
. I've tested using both Field types ofSSH_KEY
andSSHKEY
as I've seen them both mentioned in the docs/returned responses and connect-sdk-go. I ran into this issue while working on adding SSH Key support to the 1Password Terrafrom provider.The text was updated successfully, but these errors were encountered: