This is not a simple task, so if you don't know how to do this, it is highly recommended that you don't enable this option. Also, when using this option at home and your computer breaks (hard disk damaged), it is not enough to just create a new Windows account on the new installation with the same name and password you need to copy the complete account (i.e. If your Windows user account gets deleted, you won't be able to open your KeePass database anymore. If you enable this option, you can only open the database when you are logged in as the same Windows user when creating the database.īe very careful with using this option. KeeeePass can make the database dependent on the current Windows user account. OK so are you logging on using local accounts?

I am just scared to death that someone's HDD is going to fail today and be locked out of EVERYTHING. All of the info is being used in determining how to fix this risk. I might sound snarky and dismissive, but I am not. Could roll back the file from backups, but would need to know exactly when and basically we are just trading one issue (password problems) for another (key file issues) in my opinion.

A key file is great, but files get 'accidentally' changed. I have looked and looked and can't find a way for it to use the AD creds.

The only way I know of using LDAP with KeePass is to use something on the backend like Pleasant Password Server so it's KeePass but with a server serving the database and handling authentication. I thought KeePass could be configured to use a domain account - same issue if the account is deleted but a domain account is a little more 'permanent' than a local account on a computer i.e. You could use a keyfile or token like a Yubikey.

Keepass windows user account