Repository navigation
Conversation
|
The |
|
That fixed it for me. @doy can we get this merged? |
|
The fix is working well for me too. Cheers |
|
Thanks for this. In case it's useful for testing: the same field is required on |
Vaultwarden 1.37+ rejects rbw add/edit with 422 because rbw 1.15.0 omits encryptedFor (doy/rbw#385). Apply the issue's fix on top of the 1.15.0 tag until doy/rbw#386 ships. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
rbw addandrbw editcurrently fail with HTTP 422 against Vaultwarden 1.37.4+ (#385). Vaultwarden now requires anencryptedForfield on cipher create/update, matching what the official Bitwarden clients have been sending for a while.This change sends
encryptedFor(the authenticated user's UUID, as returned byGET /api/syncprofile.id) on both cipher POST and PUT. The id is stored in the local db during sync; databases created by older versions simply trigger a sync on first write, so existing setups keep working.No changes to delete/attachment/folder endpoints and no new dependencies.
Tests:
cargo build && cargo test && cargo clippy && cargo fmt --checkall pass locally.