Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Show favorites on Quick Access
It would be a great feature to show the user's favorites on the Quick Access panel. Then you could press your keyboard shortcut and arrow down to the favorite you want to auto type. This was the flow I used to use with KeePassXC and it worked nicely. Additionally, a button below the favorites to browse the whole list of items would be nice. That way, if you didn't remember what you called something and you pressed the Quick Access key you could scroll and find it.
1Password dev ressources vs IPO
Hello, since 2024, when 1Password started looking into/considered an IPO, i have the feeling all development ressources were focused solely on growing the userbase and everything else was deprioritized. For example: The terraform provider didn't get any updates (e.g. Ephemeral Values) Simple improvements are deep in the backlog: Collapsible tags Displaying the user on the "last edited" line Improvements for managing vaults/users in an enterprise context are missing: Admins still can delete Owners Vaults can be deleted by any admin without "four-eye-principle" ... There is no way to export vaults encrypted Maybe some ressources could be assigned to improvements instead of new features... /rant over
Autofill does not work with FortiClient (macOS)
My company uses FortiClient for VPN. The most common way to connect is to select a server using from the menu bar icon (I believe the app that provides that is called FortiTray) which brings up a popup browser window for logging in. 1Password does not recognize this and cannot autofill it. To make things more aggravating, the Remember Me checkbox on that window does nothing, you need to enter credentials every single time (this last part is not 1Password’s fault). Is this a known issue? Is there anything that can be done about it?1Password doesn't select public key configured in SSH config
I have two GitHub accounts and have set up my `~/.ssh/config` file per https://developer.1password.com/docs/ssh/agent/advanced#use-multiple-github-accounts. I had this set up before I started using 1Password and it has worked from the command line to differentiate between the SSH keys for my two accounts. The configuration is set up to use my default public key for my personal GitHub account and a different key is specified for my work account by: Host github.com-davies HostName github.com IdentityFile ~/.ssh/<pubkeyfilename></pubkeyfilename> NB: I added "IdentitiesOnly yes" per your documentation, but from the command line I got the error "Bad configuration option: identitesonly" so I have removed it. The key has worked from the command line without it. 1Password works fine with VSCode and command line accessing my personal GitHub account using the default public key. However, when I try accessing my work GitHub account, the 1Password prompt accesses the default key rather than the key for my work account. (It has been awhile since I have accessed my work GitHub account so I don't remember if it ever worked with 1Password). If I disable 1Password in ~/.ssh/config, SSH accesses the correct public key. My Git remote repository is configured as: remote.origin.url=git@github.com-davies:timrinkel/ Currently, the only way to access my work account is to disable 1Password and to type in the passphrase when prompted. For the record, there are other configurations, not related to GitHub or 1Password in ~/.ssh/config. MacOS: 13.7.6 1Password for Mac 8.11.1 (81101001)Storing TLS cert and general private keys in 1password
Hi I'm sure there's perhaps a good reason as to why this is not a feature, but I was wondering if there's a way to store Apple Developer certificates in 1password in a similar fashion to how we currently store and use ssh keys? The use case is that we would like to allow certain employees to have access to our Apple developer ID keys so that they can sign binaries and installer packages. At the moment we have to give them the actual private key and then of course we have no idea what happens to that key after they are done. It would be good if 1password could be brought into play in situations like this so that the key can be referenced and used on the command line and then of course the access is audited in the 1password logs. Does something like this already exist, perhaps I am not looking in the correct place? Thanks
Issues with opening the app on multiple devices
Why does the app suck so much across devices lately. I have issues on iPad, iPhone and Mac. With the app just not opening when I press on the icon or the keyboard shortcut. I’ve been through the pain with support before of diagnosing issues like this and reinstalling the app etc but I shouldn’t have too. How wide spread are these issues because I get them on every device and they come and go. They’re more common for sure on iPad and iPhone. But lately Mac is not far behind but at least with the Mac app fully closing it and restarting it pretty much always fixes the issue.
Touch ID Unlock Works in macOS Desktop App but Not in Browser Extension (Chrome/Edge)
I’m facing an issue with a user trying to use Touch ID to unlock 1Password in their browser. Touch ID works fine in the macOS desktop app, but does not function in the 1Password browser extension for either Chrome or Edge. System Info: - MacBook running latest version of macOS - 1Password desktop app: Installed and working with Touch ID - Browsers: Chrome and Edge (both up to date) - 1Password extension: Installed from Chrome Web Store / Edge Add-ons - Browser profile: Not managed (same issue occurs in fresh profiles) Problem: The browser extension does not prompt for Touch ID, even when the desktop app is unlocked and running. The extension always shows this status: Integration status: Connection problem "Please make sure the 1Password app is unlocked." The app is definitely unlocked, and this warning persists across all troubleshooting attempts. Troubleshooting Performed (in both Chrome and Edge): - Verified under Settings > Security that Touch ID is enabled - Restarted the desktop app and browser multiple times - Rebooted the system - Removed and reinstalled the 1Password browser extension - Cleared browser cache before reinstalling - Confirmed macOS, browsers, 1Password app, and extension are all up to date Would appreciate any suggestions or next steps. Happy to provide diagnostics if needed.
