[PR #6904] [MERGED] fix: add ForcePasswordReset to api key login #7503

New Issue

Closed

opened 2026-03-07 21:18:36 -06:00 by GiteaMirror · 0 comments

GiteaMirror commented 2026-03-07 21:18:36 -06:00

Owner

Copy Link

📋 Pull Request Information

Original PR: https://github.com/dani-garcia/vaultwarden/pull/6904
Author: @montdidier
Created: 3/6/2026
Status: ✅ Merged
Merged: 3/9/2026
Merged by: @dani-garcia

Base: main ← Head: fix/force-pass-reset

---

📝 Commits (1)

• 678d733 fix: add ForcePasswordReset to api key login

📊 Changes

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

View changed files

📝 src/api/identity.rs (+1 -0)

📄 Description

DESCRIPTION

This should address #5641 and #5642 if maintainers choose to merge this.

On attempting to use this patch with the Bitwarden SDK this does allow the user api key login flow to work for the login request and response at least.

Noting that full API compatibility may not the be the ultimate goal of Vaultwarden it does allow the official SDK to use this flow at least (there are obviously other missing endpoints like /api/organizations/<org_id>/secrets that do not even allow the example snippet provided with the SDK README to complete successfully).

Context: I am trying to write a CLI application - but a few challenges have made me realise I probably shouldn't be trying to leverage the official SDK to do this as I'm realistically targeting Vaultwarden more than Bitwarden proper.

The official SDK is also very poorly documented.

The offical SDK considers this field mandatory

See https://docs.rs/bitwarden-core/2.0.0/src/bitwarden_core/auth/api/response/identity_success_response.rs.html#33-34

---

_{🔄 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/6904 **Author:** [@montdidier](https://github.com/montdidier) **Created:** 3/6/2026 **Status:** ✅ Merged **Merged:** 3/9/2026 **Merged by:** [@dani-garcia](https://github.com/dani-garcia) **Base:** `main` ← **Head:** `fix/force-pass-reset` --- ### 📝 Commits (1) - [`678d733`](https://github.com/dani-garcia/vaultwarden/commit/678d73385d44b02f45bbea562ccf49677494dcae) fix: add ForcePasswordReset to api key login ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/api/identity.rs` (+1 -0) </details> ### 📄 Description **DESCRIPTION** This should address #5641 and #5642 if maintainers choose to merge this. On attempting to use this patch with the [Bitwarden SDK](https://crates.io/crates/bitwarden) this does allow the user api key login flow to work for the login request and response at least. Noting that full API compatibility may not the be the ultimate goal of Vaultwarden it does allow the official SDK to use this flow at least (there are obviously other missing endpoints like `/api/organizations/<org_id>/secrets` that do not even allow the example snippet provided with the SDK README to complete successfully). Context: I am trying to write a CLI application - but a few challenges have made me realise I probably shouldn't be trying to leverage the official SDK to do this as I'm realistically targeting Vaultwarden more than Bitwarden proper. The official SDK is also _very_ poorly documented. The offical SDK considers this field mandatory See https://docs.rs/bitwarden-core/2.0.0/src/bitwarden_core/auth/api/response/identity_success_response.rs.html#33-34 --- _{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

GiteaMirror added the pull-request label 2026-03-07 21:18:36 -06:00

GiteaMirror changed title from [PR #6904] fix: add ForcePasswordReset to api key login to [PR #6904] [MERGED] fix: add ForcePasswordReset to api key login 2026-04-16 12:36:37 -05:00

GiteaMirror closed this issue 2026-04-16 12:36:38 -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#7503