|
|
|
|
|
by maemilius
2287 days ago
|
|
I use Keeper at my current job and find it to be a horrendously bad UX. Off the top of my head: 1) The browser plugin is horribly written and has cause me numerous problems (Linux latop, YMMV), mostly related to performance and memory usage (both very bad). 2) Horrible 2FA management. You can configure Keeper to not ask you for your 2FA on a device for an hour, 30 days, or never again (iirc) and sometimes it'll just stop asking (like it did for me just now) or switch to a different 2FA for no obvious reason (I have both a security key and OTP). 3) Personal Opinion: I hate the layout of the "vault" and the browser extension's windows. I find all of them to be clunky and hard to use. On the plus side, I do like how the actual records work. Most fields are optional and they have a decent custom field system. So, you can store pretty much anything in a reasonable way (from database credentials to PII, if you're into that). |
|
The browser extension worked the best of any we trialed (this includes Dashlane, LP, Bitwarden, and 1Password).
Our users found the 2FA to be self explanatory and liked the option to use Yubikeys (when the platform supports it) and defaulting back to TOTP when not available.
The UI is simple and clear and as you pointed out the records are flexible.
Sharing is easy and the most robust of any solution we tested. (see what happens when a user you didn't intend to share with gets ahold of the share link in LastPass).
Data replication between uses and devices was near instantaneous with no user action to ensure the vault was in sync.
Additionally, we subscribe to BreachWatch and have gotten immense value in knowing that our users are not using breached credentials.
One final note from an enterprise perspective, the admin console for Keeper was clearly the easiest to use with the most features of any of the solutions we trialed.