Ian

@clue I'm happy to help out with vetting some of the PRs. Did you end up giving anyone else committer access yet?

@davkal I wrote a patch (referenced in this PR), but want to verify it. Any idea how I can reproduce using the test page? I'm not quite familiar enough with...

LDAP syncing has been added to the wiki: https://github.com/dani-garcia/bitwarden_rs/wiki/Syncing-users-from-LDAP

@KreativeKrise can't you already store your configuration in a file and mount that using Docker Secrets? Also you can do what that blog suggests already without an upstream patch. This...

@tckb there are other containers you could attach to Bitwarden_rs for backups. I'm using images that I built for Duplicity and Restic for doing exactly what you're talking about. -...

@tckb wow. I really ought to switch to k8s, hah. That's super handy. I've been using [Dockron](https://blog.iamthefij.com/2018/11/19/introducing-dockron-scheduling/) to get something similar (cron schedules to update my ddns and renew certs),...

@tckb for now just Docker Compose directly on each host and I use Ansible to orchestrate. I'm using Backblaze B2 for storage. It's convenient and affordable. Both Duplicity and Restic...

It is not possible to use LDAP as the sole form of authentication without sacrificing client side decryption. At least not without completely rewriting the client applications. I don't know...

@alfonsrv biggest reason is password change. You have to maintain two passwords, which will require a client change.

@alfonsrv yes. That’s then two passwords anyway. Today, nothing stops you from changing your Bitwarden password to your LDAP password. This was discussed earlier (in this thread or another), but...