Skip to content

SQLite / PostgreSQL behavior difference related to the archivedDate field #7581

Description

@AChep

Prerequisites

Vaultwarden Support String

Vaultwarden Build Version

1.37.1

Deployment method

Official Container Image

Custom deployment method

No response

Reverse Proxy

Host/Server Operating System

Linux

Operating System Version

No response

Clients

CLI

Client Version

Steps To Reproduce

Updating an archived cipher through PUT /api/ciphers/{id} with:

{
  "archivedDate": null,
  ...
}

Expected Result

The official Bitwarden server does unarchvie the item in that case, so I assume that is the intended behavior.

Actual Result

Appears to unarchive the cipher on SQLite but on PostgreSQL, the same request leaves the cipher archived.

Logs


Screenshots or Videos

No response

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions