Developers

I have 1Password set to auto-lock after 10 minutes of inactivity. This means that in my daily workflow, I need to re-type my password every time I perform an SSH operation such as interacting with git remotes etc... This gets annoying pretty fast, and the options to avoid this are not ideal: - Set 1Password to never lock after inactivity, which is less secure - Don't use 1Password for ssh keys that are used often (multiple times an hour) Would it be possible to have a way to allow certain keys to be used even when 1Password is locked? 1Password Version: Not Provided Extension Version: Not Provided OS Version: Not Provided

I just saw the post & beta for SSH + CLI integration and this seems amazing. +1 Cant wait for the final release. However, I'm unable to get this working at all. * I also use a shell called fishshell for what it's worth. (fish, version 3.3.1, but I do not believe this is part of the issue, as I swapped to bash too, and experience the same issue) * I have installed OpenSSH (OpenSSH_8.6p1) * 1P CLI is on version 2.0.0 I've run both the "configuration" commands per the docs. I've created the symlink using mkdir -p ~/.1password && ln -s ~/Library/Group\ Containers/2BUA8C4S2C.com.1password/t/agent.sock ~/.1password/agent.sock ...and added the additional line to the ssh config Host * IdentityAgent "~/.1password/agent.sock" IdentitiesOnly yes I also added the SSH_AUTH_SOCK to my profile, even tried the global config from https://developer.1password.com/docs/ssh/agent/compatibility#configure-ssh_auth_sock-globally-for-every-client I've check that I have all the requi

I've looked and nothing seems to work with current versions of ITerm2 and 1Password on Monterey. Am I just looking in the wrong place? 1Password Version: Not Provided Extension Version: Not Provided OS Version: Not Provided Referrer: forum-search:https://1password.community/search?Search=iterm2

I'm configuring the CLI for the first time, and I was surpresed to see that op account add shows the Secret Key as I type it (same for op vault ls). For such a sensitive secret, it should definitely not be shown in the terminal! 1Password Version: Not Provided Extension Version: Not Provided OS Version: Not Provided

Using 1Password command-line tool 1.12.4. I’ve got temporary access to a vault in ACCOUNT2 so that I can copy the entries to ACCOUNT1. They didn’t set up my account permissions to have right-click "copy item" support so that I could do this in the GUI, so I exported everything using op: op list items --account ACCOUNT2 | op get item - > ACCOUNT2.jsonl I did the same thing (more or less) with op list documents (there are two attached documents). I’ve split the individual line entries into multiple single JSON files and want to create them in the new account more or less like this: op create item --account ACCOUNT1 --vault VAULTNAME --template item1.json This didn’t work initially because of the missing category. So I modified it: op create item --account ACCOUNT1 --vault VAULTNAME --template item1.json Password This worked, but not really. It was imported as "Untitled Password", despite the fact that there is a details.title field. So I decided to try something else:

Can't seem to get DigitalOcean connected. Tried both Ed25519 and RSA. I also cleared out all entries in known_hosts. % ssh root@{server-ip} Received disconnect from {server-ip} port 22:2: Too many authentication failures Disconnected from {server-ip} port 22 Anyone else have any luck? 1Password Version: 8.7.0 Extension Version: 2.3.2 OS Version: macOS 12.3

I've just installed the SSH Agent as specified under the install documents but am currently unable to enable the agent. With the OpenSSH Agent disabled and the SSH Beta enabled in the .json, I am not seeing the option to enable as it remains greyed out. I did not follow the Git setup as Git is not part of our stack/my use case. Is step 2 (Setup Git) required? 1Password Version: 8.6.0 Extension Version: 2.3.0 OS Version: W10-21H2 19044.1526

When trying to import a private key that has no passphrase, I am unable to continue beyond this screen: 1Password Version: Not Provided Extension Version: Not Provided OS Version: Not Provided

Since the Apt install is failing for me I'm trying a manual install instead, but verification is failing for me: ➜ gpg --receive-keys 3FEF9748469ADBE15DA7CA80AC2D62742012EA22 gpg: key AC2D62742012EA22: new key but contains no user ID - skipped gpg: Total number processed: 1 gpg: w/o user IDs: 1 ➜ gpg --verify op.sig op gpg: Signature made Thu 10 Mar 2022 11:19:58 PM CET gpg: using RSA key 3FEF9748469ADBE15DA7CA80AC2D62742012EA22 gpg: Can't check signature: No public key 1Password Version: CLI 2.0.0 Extension Version: n/a OS Version: Raspberry Pi OS (bullseye, 32 bits)

The Windows tab https://developer.1password.com/docs/cli/get-started/ has an incorrect URL, in the section 'To install 1Password CLI with a single block of commands, run the following in Powershell as administrator:' $env:ARCH="<choose between 386/amd64>"; ` Invoke-WebRequest "https://cache.agilebits.com/dist/1P/op2/pkg/v2.0.0/op_$($env:ARCH)_v2.0.0.zip" -OutFile op.zip; ` Expand-Archive op.zip -DestinationPath "C:\Program Files\1Password CLI"; ` [Environment]::SetEnvironmentVariable("PATH", "$([System.Environment]::GetEnvironmentVariable('PATH','machine'));C:\Program Files\1Password CLI", "Machine"); ` Remove-Item "op.zip" The Invoke-WebRequest cmdlet has the URL: "https://cache.agilebits.com/dist/1P/op2/pkg/v2.0.0/op_$($env:ARCH)_v2.0.0.zip" but it should be: "https://cache.agilebits.com/dist/1P/op2/pkg/v2.0.0/op_windows_$($env:ARCH)_v2.0.0.zip" The command block will also add more than one 'C:\Program Files\1Password CLI' entry into PATH if ran multiple times. I can unde

👋 Welcome everyone! Today we’re stoked to announce our first early access for 1Password’s CLI 2.0! We have spent the last 6 months taking the time to reimagine the future of the CLI for administrators and developers using this tool and we can’t wait to have you test what we’ve been working on. Housekeeping: Please keep in mind that this is an early access so your feedback and insights are crucial to helping us perfect this new version of the CLI. We're user-feedback driven and your questions, comments and advice will help us shape a final version that impacts your daily workflows and makes your day-to-day easier. On the Forum, feel free to create threads anytime you have a question, concern or just product feedback that you’d like to share. You’ll find your fellow testers and 1Password engineers will join in! Our Product and Engineering teams will also be active within this private forum to 1) answer any questions you have and 2) most importantly - listen to your thoughts! W

The recently released SSH key management feature got me thinking, would it be useful to have a client certificate management feature in 1Password? It would greatly simplify the generation and distribution for small businesses which don't have a full-fledged PKI solution. 1Password Version: Not Provided Extension Version: Not Provided OS Version: Not Provided

Hey folks 👋 

If you haven’t seen the big news by now, we have officially taken CLI 2.0 out of beta and released it today 😄 We are incredibly appreciative of everyone here who has taken the time to give us so much valuable feedback on CLI and help us shape the future of this amazing tool. 

 If you’d like to read Dave’s announcement blog https://blog.1password.com/1password-cli-2.0/. 

As we move forward after our launch today, I will be keeping this forum open as we have another CLI beta kicking off soon and would love the same amazing folks who have been giving us feedback on 2.0 to give us even more feedback on a brand new feature. 

In addition, we still have quite a few gift cards to give out and anyone who shares insightful feedback will be considered for one of those awesome rewards. We’ve already given out several $500 USD gift cards to Amazon and other places so stay tuned for a beta announcement soon so that you have a chance to win one of those. 

Thank you again for

Hey folks 👋 If you haven’t seen the big news by now, we have officially taken SSH out of beta and released it “into the wild” 😄We are incredibly appreciative of everyone here who has taken the time to be the first beta testers to get their hands on SSH and all of the feedback that you’ve given us has been instrumental in helping us get to today’s milestone. If you’d like to read Dave’s announcement blog https://blog.1password.com/1password-ssh-agent/. Going forward, I’d like to keep this forum group open as we will have some more things to test shortly within a few weeks specific to SSH and we’d love to continue this group (and add even more developers to it). You all have been incredibly gracious with your time and been amazing at starting new threads and giving us so much quality feedback. So going forward, stay tuned for more news and things to test for SSH in this forum as we still have quite a few gift cards to give out to folks going forward for insightful pieces of feedba

Want to hear some exciting news? The SSH beta is officially underway and we'd love to have you get started right away with testing out 1Password's SSH key management solution. However, before you jump immediately into the documentation, lets go over what you can test as part of this beta: SSH key item with key generation and import support SSH public key autofill in the 1Password Browser extension SSH agent with biometrics support We have been testing the agent internally and have seen so much positive feedback on how it has helped improve our developer's workflows. Once your keys are safely stored within 1Password as SSH key items, the agent will work with your existing clients so that you can use your keys within your day to day workflows. To get started on testing out these new features please head on over to https://developer.1password.com/docs/ssh. Just as we’re looking for feedback on the SSH feature, we also want to hear your thoughts on the new docs. Let us know how thing

Having some trouble figuring out this issue. I'm using the REST API to send requests to our Connect server. Accessing 1password through the browser I set up a test vault with two items. Using the API, I send a GET request to /v1/vaults/{vaultUUID}/items and it returns the two items Next I send a POST request to the same endpoint with an object and I verify that the item has been created successfully in the vault. There are now three items in the vault. When I send a GET request again, however, it only shows the two items from before. Could this be a cache issue? 1Password Version: Not Provided Extension Version: Not Provided OS Version: Not Provided

Hey folks 👋 I wanted to make sure that everyone was aware that we’ll be doing a Reddit AMA on Thursday, March 17th at 12PM Eastern to answer all of your questions about our Developer Tools launch. We’ll have our Product and Engineering teams live to answer anything you have questions on regarding SSH, CLI 2.0, our new Developer Documentation Portal and anything else that you’d love to see us build for developers moving forward. 1Password has always led with listening to our customers and hearing their opinions so we'll see you there on the 17th in Reddit so that we can have an awesome conversation with you 😄 https://www.reddit.com/r/1Password/comments/te7217/were_the_team_behind_1password_developer_tools/ if you’d like to post any of your questions in advance. We can't wait to see you there!

When I try to import one of my SSH private keys (either from a file or through the system's clipboard), 1Password keeps saying that the passphrase I provide is wrong. Providing the same passphrase, when adding another key with the same passphrase, works fine. I'm able to add the key to the macOS default SSH agent: bash $ ssh-add ~/.ssh/someone@example.com Enter passphrase for /Users/mstrzele/.ssh/someone@example.com: Identity added: /Users/mstrzele/.ssh/someone@example.com (/Users/mstrzele/.ssh/someone@example.com) $ ssh-add -l 4096 SHA256:VYZx99XD1lBZIDd8bgnSgMLpIQ4MQfx8wSidaL9ES1c /Users/mstrzele/.ssh/someone@example.com (RSA) I can't add the key to the agent provided by 1Password, though: bash $ echo "$SSH_AUTH_SOCK" /Users/mstrzele/Library/Group Containers/2BUA8C4S2C.com.1password/t/agent.sock $ ssh-add ~/.ssh/someone@example.com Enter passphrase for /Users/mstrzele/.ssh/someone@example.com: Could not add identity "/Users/mstrzele/.ssh/someone@example.com": agent refused operat

I have one (ed25519) SSH key that I use to log in to multiple devices. This used to work fine, but as of today only the first login succeeds. When I try to log in to a second or third machine I get this error: Load key "/Users/me/.ssh/ed25519.pub": invalid format me@domain.com: Permission denied (publickey). Coincidentally 1Password then auto-updated. Now I could log in to the second machine using the same key, but not the third. So it looks like that a SSH key is now only working once per 1Password session? 1Password Version: 80600066 (Nightly) Extension Version: n/a OS Version: macOS Monterey 12.2.1

I was trying to download all the documents of a particular vault using the golang sdk, I noticed that a few files were not downloaded and when I checked the docker logs for the connect API service I saw the error log_message":"(W) Server: (failed to GetFileWithUUID), attempting to decrypt message with KID using KID , client used wrong Key","timestamp":"2022-02-21T07:23:18.570941261Z I'm using the method client.GetFileContent() to get the file content I also saw a old post for the cli : https://1password.community/discussion/87002/op-get-document-fails-with-a-500-error , I think it might be the same issue, I re-uploaded the file and the issue was solved but Is there a way I can gracefully handle this in code without the need to re-upload the file? 1Password Version: gosdk-v1.2.0 Extension Version: Not Provided OS Version: Ubuntu 20.04.2 LTS

Hi, I noticed that the password field returns the history of the password (the following password values are, obviously, fictitious) { "id": "password", "type": "CONCEALED", "purpose": "PASSWORD", "label": "password", "value": "kdsjlasj", "entropy": 317.9739685058594, "passwordDetails": { "entropy": 317, "generated": true, "strength": "FANTASTIC", "history": [ "dkljsfojfsado" ] } } However, it would be very useful for auditing purposes if we could monitor the exact times _when _ the password was changed through the API. This information is available in the GUI, but I can't seem to find an API endpoint that exposes this information. I'm running 1Password Connect API version 1.5.0, is there an endpoint that can give us that information? If not, is this something that could

I have found that under some circumstances when I am required to approve the use of a SSH key, sometimes it doesn't bring the app to the front of the screen and I don't see the approval prompt. Other times 1Password is on my second screen whilst I am working on my primary screen and again I don't see the approval prompt. Could we add the choice to allow the bouncing dock icon on MACOS when there is an approval prompt similar to the similar option in Slack "Bounce Slack's icon when receiving a notification" 1Password Version: 8.6.0 (80600051) Extension Version: Not Provided OS Version: MACOS 12.2.1

Hi, I have the SSH beta on one machine so far. I spoted my first SSH key showing in 1Password on my other machine and it showed the "Next steps" box at the top of the item in order to enable the 1PW Agent. When clicking the button to open preferences, it opens the window but due to the SSH beta not being enabled in this version, the preferences window was just blank leaving me at a dead end. I realise this is most likely just due to the beat not being enabled on that machine but it is in effect a bug, albeit a minor, side effect-y type of bug. 1Password Version: Not Provided Extension Version: Not Provided OS Version: Not Provided

Hi, Going by the comment by @Enceladus in this topic: https://1password.community/discussion/comment/631622#Comment_631622 Could the info in the following window be updated to include details on setting the ENV variable as well? Thanks! 1Password Version: Not Provided Extension Version: Not Provided OS Version: Not Provided

I used to use an app called https://github.com/kryptco/kr to provide the 2nd-factor SSH login approval functionality that 1Password is now providing. One thing it had was the ability to set certain hosts as "always approved" so that you didn't have to manually approve every login. This is particularly useful in the case of say, a Git client using SSH to connect to GitHub or GitLab, where the sensitivity of the connection is less than say, a production server. It would be great to have that feature here as well because currently, I have to approve connections constantly from my terminal, Git client, and IDE. 1Password Version: Not Provided Extension Version: Not Provided OS Version: Not Provided