5 ms·

There isn't a perfect solution, but LastPass Entrprise or a similar service is probably the closest you're going to get. KeePass is great, but it's a single us

There isn't a perfect solution, but LastPass Entrprise or a similar service is probably the closest you're going to get. KeePass is great, but it's a single user solution. --Even I have to be careful about forgetting to save the database after adding a new entry at work and then going home and adding something else there. You shouldn't even be entertaining the idea of a Google Docs sheet or an Excel file in Dropbox when you're dealing with client passwords. That's just asking for trouble.

Ecio78 14y ago
We use KeePass as a multi-user solution: the kdb file is on a network share (with relevant ACLs). The only thing you have to take into account is that you dont have to leave it opened on your computer, so the typical use is: Open / Read (or Write) Password / Close it. It works in small groups (we're three guys using it, two more frequently)
- estel 14y ago
  We do something similar, but with relatively few users using Keepass 2, there aren't really any issues with leaving it open on multiple machines. Is there an issue besides synchronisation?
  - Ecio78 14y ago
    afaik the second user should open it read only, so it cant update (that's why I was saying that the user should close it after having read/written some data)
    - estel 14y ago
      That was true for Keepass 1, but since 2 I think everyone can open it read/write? I think I'm prompted to "synchronise" when I save if another user has saved since I first opened it.
      - tallanvor 14y ago
        Ah, if KeePass v2 allows for synchronization, then that solves the big problem of people overwriting each other. Although I would probably still suggest a solution that allows more granular access controls and doesn't require everyone to share the same password for logging in.
robin_reala 14y ago
LastPass Enterprise is working well enough for our organisation. The only thing I dislike about it is that I have a personal LastPass account and can’t keep them both logged in at the same time through the browser plugin.
- robin_reala 14y ago
  Of course, today a colleague pointed out that from within your enterprise account you can ‘link your personal account’ from the let sidebar. That was my last gripe really (apart from the front-end code needing an overhaul).

Ecio78 14y ago

We use KeePass as a multi-user solution: the kdb file is on a network share (with relevant ACLs). The only thing you have to take into account is that you dont have to leave it opened on your computer, so the typical use is: Open / Read (or Write) Password / Close it. It works in small groups (we're three guys using it, two more frequently)

estel 14y ago
We do something similar, but with relatively few users using Keepass 2, there aren't really any issues with leaving it open on multiple machines. Is there an issue besides synchronisation?
- Ecio78 14y ago
  afaik the second user should open it read only, so it cant update (that's why I was saying that the user should close it after having read/written some data)
  - estel 14y ago
    That was true for Keepass 1, but since 2 I think everyone can open it read/write? I think I'm prompted to "synchronise" when I save if another user has saved since I first opened it.
    - tallanvor 14y ago
      Ah, if KeePass v2 allows for synchronization, then that solves the big problem of people overwriting each other. Although I would probably still suggest a solution that allows more granular access controls and doesn't require everyone to share the same password for logging in.

robin_reala 14y ago

LastPass Enterprise is working well enough for our organisation. The only thing I dislike about it is that I have a personal LastPass account and can’t keep them both logged in at the same time through the browser plugin.

robin_reala 14y ago
Of course, today a colleague pointed out that from within your enterprise account you can ‘link your personal account’ from the let sidebar. That was my last gripe really (apart from the front-end code needing an overhaul).