The UserDecryption values are not only returned on the authentication response, but also on calls to /sync, which I've missed on #6572.
Yes, it's also using different casing 😿, but that's the behavior from upstream, so I'd rather copy it to avoid problems
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/dani-garcia/vaultwarden/pull/6574
**Author:** [@dani-garcia](https://github.com/dani-garcia)
**Created:** 12/19/2025
**Status:** ✅ Merged
**Merged:** 12/19/2025
**Merged by:** [@dani-garcia](https://github.com/dani-garcia)
**Base:** `main` ← **Head:** `more-user-decryption-options`
---
### 📝 Commits (1)
- [`80e2250`](https://github.com/dani-garcia/vaultwarden/commit/80e2250917425605f487f376288e06e9f4983159) Add UserDecryptionOptions on /sync too
### 📊 Changes
**2 files changed** (+25 additions, -4 deletions)
<details>
<summary>View changed files</summary>
📝 `src/api/core/ciphers.rs` (+22 -1)
📝 `src/api/core/mod.rs` (+3 -3)
</details>
### 📄 Description
The UserDecryption values are not only returned on the authentication response, but also on calls to /sync, which I've missed on #6572.
Yes, it's also using different casing 😿, but that's the behavior from upstream, so I'd rather copy it to avoid problems
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/dani-garcia/vaultwarden/pull/6574
Author: @dani-garcia
Created: 12/19/2025
Status: ✅ Merged
Merged: 12/19/2025
Merged by: @dani-garcia
Base:
main← Head:more-user-decryption-options📝 Commits (1)
80e2250Add UserDecryptionOptions on /sync too📊 Changes
2 files changed (+25 additions, -4 deletions)
View changed files
📝
src/api/core/ciphers.rs(+22 -1)📝
src/api/core/mod.rs(+3 -3)📄 Description
The UserDecryption values are not only returned on the authentication response, but also on calls to /sync, which I've missed on #6572.
Yes, it's also using different casing 😿, but that's the behavior from upstream, so I'd rather copy it to avoid problems
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.