|
I can't offer consensus, but I can relate my experience. I recently purchased 1Password for Teams based on previous discussions of its design merits relative to tools like PasswordSafe and KeePass (both of which I've used in the past), and I've deployed it across Windows, macOS, and iOS clients and used it with Firefox, Safari, and Chrome, in addition to making regular use of the in-browser web app (which is required in order to manage the team). From the user's perspective, the macOS and iOS clients work the best in that they support all of the 1Password client-side features (adding/editing custom fields being the one I use the most). The macOS version of the browser plugin has a great UI, in that one can quickly access/edit the different credential record fields via its pop-up window. Neither Windows client nor the Windows browser plugin seems to be as flexible or as polished. Until very recently it wasn't possible to add custom fields (one had to log into 1Password via the in-browser client or use the macOS/iOS client to do things like add a TOTP credential), and the browser plugin's UI is slow and more difficult to use compared to the macOS version. While the Windows client comes packaged as an MSI, I believe that it only supports per-user installs, which prevented me from deploying it using our enterprise configuration management system. Ultimately, it seems like the Windows client and browser plugin aren't supported as well as the macOS/iOS versions, which has ended up slowing our adoption of the software as most of our users run Windows (I'm getting ready to transition away from macOS myself). The team management features of 1Password work well, but one can only access them via the in-browser web app as neither the client nor the browser plugin provide access to those features. So far I haven't run into any synchronization problems, and that includes using it in some out-of-the-way places with poor network connectivity (high latency/high packet loss/low bandwidth). Because I was using KeePass, I could not use 1Password's built-in migration tool. Their third-party migration tool (which I grabbed from their GitHub repo) worked smoothly. Overall, 1Password for Teams works better than the mix of KeePass and ownCloud I was using before (not to mention the questionable third-party ports of KeePass to iOS/Android or the fact that KeePass did not work at all when run under Mono on macOS). Despite the limitations and relatively poor performance of their Windows offerings (my biggest issues with the product), I will likely renew our subscription this year. |