4 ms·

Been a huge fan of KeePass for years and recommend it to anyone that listens. I created EnterPass (https://enterpass.co https://enterpass.co) based on the flex

Been a huge fan of KeePass for years and recommend it to anyone that listens. I created EnterPass (https://enterpass.co https://enterpass.co) based on the flexibility, simplicity and security of KeePass. It's for companies to manage passwords across teams and want to keep the passwords stored inside their own networks... not on the cloud. Oh, and you don't need to remember a master password to use it as it uses Active Directory for permissions. KeePass has been a huge influence.

Roritharr 10y ago
I can see why you are being downvoted, but this is a huge problem so many organizations face that i'm getting mad that there's no "just use x" solution when you need Keepass for organizations, with sharing, access groups etc. Not everything can be handled by attaching LDAP.
- _Understated_ 10y ago
  Agreed, hence the reason I built my own but as for LDAP, it's used for access to a gazillion things in the network already, e.g. file shares, applications, internet access and so on that surely using it to authorise access to one more resource, passwords in this case, makes sense. Active Directory makes it easy to authorize/authenticate so surely that would be a good thing.
  - Roritharr 10y ago
    Oh sorry, i didn't mean to say that attaching it is wrong, i meant that you can't attach it to every piece of Software/Web-App which would indeed be nice. Logging into the Company Bankaccount with LDAP would be nice.
    - _Understated_ 10y ago
      Ah, that makes sense :)
jobigoud 10y ago
I don't quite understand the need. We used KeePass on the network where I worked previously. The kdb file was simply stored on the network. We had a few of those for various level of access. You did have to remember those few master passwords for for the files you had access to, but it gave another level of flexibility by not being tied to AD.

Roritharr 10y ago

I can see why you are being downvoted, but this is a huge problem so many organizations face that i'm getting mad that there's no "just use x" solution when you need Keepass for organizations, with sharing, access groups etc. Not everything can be handled by attaching LDAP.

_Understated_ 10y ago
Agreed, hence the reason I built my own but as for LDAP, it's used for access to a gazillion things in the network already, e.g. file shares, applications, internet access and so on that surely using it to authorise access to one more resource, passwords in this case, makes sense. Active Directory makes it easy to authorize/authenticate so surely that would be a good thing.
- Roritharr 10y ago
  Oh sorry, i didn't mean to say that attaching it is wrong, i meant that you can't attach it to every piece of Software/Web-App which would indeed be nice. Logging into the Company Bankaccount with LDAP would be nice.
  - _Understated_ 10y ago
    Ah, that makes sense :)

jobigoud 10y ago

I don't quite understand the need. We used KeePass on the network where I worked previously. The kdb file was simply stored on the network. We had a few of those for various level of access. You did have to remember those few master passwords for for the files you had access to, but it gave another level of flexibility by not being tied to AD.