Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs
text/plain API responses to application/json by @jjlin in https://github.com/dani-garcia/vaultwarden/pull/3124
shrink-to-fit=no from viewport-meta-tag by @redwerkz in https://github.com/dani-garcia/vaultwarden/pull/3126
arm32v6-specific tag by @jjlin in https://github.com/dani-garcia/vaultwarden/pull/3164
/api/devices/knowndevice with HTTP header params by @jjlin in https://github.com/dani-garcia/vaultwarden/pull/3329
Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.27.0...1.28.0
With this feature enabled, actions occurring inside an organization will be recorded in a log, viewable by organization admins and owners. Check the official documentation to learn more: https://bitwarden.com/help/event-logs/ (Note that the Public API is not yet implemented, so the events are only viewable in the Web Vault)
To enable this feature, set ORG_EVENTS_ENABLED=true. By default all events will be stored indefinitely, if you want to limit that, you can use the EVENTS_DAYS_RETAIN option. You can also tune the cleanup schedule with EVENT_CLEANUP_SCHEDULE.
Enables the creation and use of groups inside an organization. At the moment this is in beta because there are some known issues (https://github.com/dani-garcia/vaultwarden/issues/2989). Still, the more this feature is tested, the faster we will be able to stabilize it.
To enable this feature, set ORG_GROUPS_ENABLED=true, make sure to make proper backups of your instance before hand.
ROCKET_ADDRESS into account in the Docker healthcheck by @jjlin in https://github.com/dani-garcia/vaultwarden/pull/2844
/devices/knowndevice endpoint by @BlackDex in https://github.com/dani-garcia/vaultwarden/pull/2893
register endpoint to identity by @BlackDex in https://github.com/dani-garcia/vaultwarden/pull/2920
left_join by @BlackDex in https://github.com/dani-garcia/vaultwarden/pull/2976
Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.26.0...1.27.0
CreationDate to cipher response JSON by @jjlin in https://github.com/dani-garcia/vaultwarden/pull/2813
Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.25.2...1.26.0
⚠️ Reminder: If you are still using the bitwardenrs/server* Docker images, you need to migrate to the new vaultwarden image. Check https://github.com/dani-garcia/vaultwarden/discussions/1642 for an explanation. The old images will not receive any new updates any longer.
An incompatibility between the format in which some Bitwarden clients upload attachments and sends could lead to those uploads being silently corrupted. We believe this is occurring only when using the mobile clients and only on the latest vaultwarden 1.25.1. To mitigate this issue, we're releasing this quick patch to make any upload that could lead to a corrupted file explicitly return an error, notifying the user of the problem. We recommend updating as soon as possible, and checking that any recently uploaded attachments can be downloaded and opened correctly (The corrupted uploads will return an error when downloading or download a very small file).
We've also fixed the docker volume check added in 1.25.1, if you previously needed to set I_REALLY_WANT_VOLATILE_STORAGE=true to start the container, please try again without it, and open an issue if it still won't start.
Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.25.1...1.25.2
⚠️ Reminder: If you are still using the bitwardenrs/server* Docker images, you need to migrate to the new vaultwarden image. Check https://github.com/dani-garcia/vaultwarden/discussions/1642 for an explanation. The old images will not receive any new updates any longer.
password_hints_allowed config option by @jjlin in https://github.com/dani-garcia/vaultwarden/pull/2586
Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.25.0...1.25.1
⚠️ Reminder: If you are still using the bitwardenrs/server* Docker images, you need to migrate to the new vaultwarden image. Check https://github.com/dani-garcia/vaultwarden/discussions/1642 for an explanation. The old images will not receive any new updates any longer.
/api/{alive,now,version} endpoints by @jjlin in https://github.com/dani-garcia/vaultwarden/pull/2433
Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.24.0...1.25.0
⚠️ Reminder: If you are still using the bitwardenrs/server* Docker images, you need to migrate to the new vaultwarden image. Check https://github.com/dani-garcia/vaultwarden/discussions/1642 for an explanation. The old images will not receive any new updates any longer.
Expires header when caching responses by @RealOrangeOne in https://github.com/dani-garcia/vaultwarden/pull/2182
Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.23.1...1.24.0
⚠️ Reminder: If you are still using the bitwardenrs/server* Docker images, you need to migrate to the new vaultwarden image. Check https://github.com/dani-garcia/vaultwarden/discussions/1642 for an explanation. The old images will not receive any new updates any longer.
read_only and hide_passwords flags by @jjlin in https://github.com/dani-garcia/vaultwarden/pull/2073
Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.23.0...1.23.1
⚠️ Reminder: If you are still using the bitwardenrs/server* Docker images, you need to migrate to the new vaultwarden image. Check https://github.com/dani-garcia/vaultwarden/discussions/1642 for an explanation. The old images are deprecated and will stop being updated after 1.23.0.
EMERGENCY_ACCESS_ALLOWED=false
/alive endpoint⚠️ Reminder: If you are still using the bitwardenrs/server* Docker images, you need to migrate to the new vaultwarden image. Check https://github.com/dani-garcia/vaultwarden/discussions/1642 for an explanation. The old images are deprecated and will stop being updated after 1.23.0.
show_password_hint by default, it still can be enabled in the admin panel or with environment variables.