[PR #7045] [CLOSED] Add authType field to Send API responses #36991

New Issue

Closed

opened 2026-07-13 21:31:09 -05:00 by GiteaMirror · 0 comments

GiteaMirror commented 2026-07-13 21:31:09 -05:00

Owner

Copy Link

📋 Pull Request Information

Original PR: https://github.com/dani-garcia/vaultwarden/pull/7045
Author: @jalenfran
Created: 4/1/2026
Status: ❌ Closed

Base: main ← Head: main

---

📝 Commits (1)

• f3ecc8c Add authType field to Send API responses

📊 Changes

1 file changed (+4 additions, -0 deletions)

View changed files

📝 src/db/models/send.rs (+4 -0)

📄 Description

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)

---

_{🔄 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/7045 **Author:** [@jalenfran](https://github.com/jalenfran) **Created:** 4/1/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (1) - [`f3ecc8c`](https://github.com/dani-garcia/vaultwarden/commit/f3ecc8c7bdb0e0e6d1adcce968524a8840630a2d) Add authType field to Send API responses ### 📊 Changes **1 file changed** (+4 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/db/models/send.rs` (+4 -0) </details> ### 📄 Description 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) --- _{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

GiteaMirror added the pull-request label 2026-07-13 21:31:09 -05:00

GiteaMirror closed this issue 2026-07-13 21:31:10 -05:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

revert-7033-patch-1

cached-config-operations

test_dylint

1.36.0

1.35.8

1.35.7

1.35.6

1.35.5

1.35.4

1.35.3

1.35.2

1.35.1

1.35.0

1.34.3

1.34.2

1.34.1

1.34.0

1.33.2

1.33.1

1.33.0

1.32.7

1.32.6

1.32.5

1.32.4

1.32.3

1.32.2

1.32.1

1.32.0

1.31.0

1.30.5

1.30.4

1.30.3

1.30.2

1.30.1

1.30.0

1.29.2

1.29.1

1.29.0

1.28.1

1.28.0

1.27.0

1.26.0

1.25.2

1.25.1

1.25.0

1.24.0

1.23.1

1.23.0

1.22.2

1.22.1

1.22.0

1.21.0

1.20.0

1.19.0

1.18.0

1.17.0

1.16.3

1.16.2

1.16.1

1.16.0

1.15.1

1.15.0

1.14.2

1.14.1

1.14

1.13.1

1.13.0

1.12.0

1.11.0

1.10.0

1.9.1

1.9.0

1.8.0

1.7.0

1.6.1

1.6.0

1.5.0

1.4.0

1.3.0

1.2.0

1.1.0

1.0.0

0.13.0

0.12.0

0.11.0

0.10.0

0.9.0

Labels

Clear labels

better for forum

bug

documentation

duplicate

enhancement

future Vault

good first issue

help wanted

low priority

notes

pull-request

Mirrored from GitHub Pull Request

question

SSO

Third party

troubleshooting

wontfix

No Label pull-request

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

GiteaMirror ninjasurge

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#36991