Add authType field to Send API responses #5

New Issue

MrUnknownDE · 2026-04-05T20:28:55+02:00

MrUnknownDE commented

2026-04-05 20:28:55 +02:00

Originally created by @jalenfran on 4/1/2026

Fixes #6976

Problem

All Sends were displaying as password-protected in the web vault regardless of their actual protection status.

Root Cause

The web-vault changed how it determines Send protection status in bitwarden/clients@9f74178. It now checks authType !== AuthType.None instead of checking for the presence of the password field, but Vaultwarden wasn't returning authType in its API responses.

Fix

Add authType to Send.to_json() using Bitwarden's AuthType enum:

0 = Email (future email OTP support)
1 = Password protected
2 = None (no authentication required)

*Originally created by @jalenfran on 4/1/2026* Fixes #6976 ## Problem All Sends were displaying as password-protected in the web vault regardless of their actual protection status. ## Root Cause The web-vault changed how it determines Send protection status in bitwarden/clients@9f74178. It now checks `authType !== AuthType.None` instead of checking for the presence of the `password` field, but Vaultwarden wasn't returning `authType` in its API responses. ## Fix Add `authType` to `Send.to_json()` using Bitwarden's `AuthType` enum: - `0` = Email (future email OTP support) - `1` = Password protected - `2` = None (no authentication required)

MrUnknownDE closed this issue

2026-04-05 20:28:55 +02:00

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/vaultwarden#5