[PR #2245] [MERGED] Add support for API keys #3072

New issue

Closed

opened 2026-03-03 09:25:43 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 09:25:43 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/dani-garcia/vaultwarden/pull/2245
Author: @jjlin
Created: 1/19/2022
Status: ✅ Merged
Merged: 1/23/2022
Merged by: @dani-garcia

Base: main ← Head: api-key

📝 Commits (2)

69ee4a7 Add support for API keys
8f79007 Fix scope and refresh_token for API key logins

📊 Changes

14 files changed (+182 additions, -17 deletions)

View changed files

➕ migrations/mysql/2022-01-17-234911_add_api_key/down.sql (+0 -0)
➕ migrations/mysql/2022-01-17-234911_add_api_key/up.sql (+2 -0)
➕ migrations/postgresql/2022-01-17-234911_add_api_key/down.sql (+0 -0)
➕ migrations/postgresql/2022-01-17-234911_add_api_key/up.sql (+2 -0)
➕ migrations/sqlite/2022-01-17-234911_add_api_key/down.sql (+0 -0)
➕ migrations/sqlite/2022-01-17-234911_add_api_key/up.sql (+2 -0)
📝 src/api/core/accounts.rs (+36 -3)
📝 src/api/identity.rs (+94 -11)
📝 src/crypto.rs (+28 -0)
📝 src/db/models/device.rs (+7 -2)
📝 src/db/models/user.rs (+8 -1)
📝 src/db/schemas/mysql/schema.rs (+1 -0)
📝 src/db/schemas/postgresql/schema.rs (+1 -0)
📝 src/db/schemas/sqlite/schema.rs (+1 -0)

📄 Description

This is mainly useful for CLI-based login automation.

Upstream PR: https://github.com/bitwarden/server/pull/981
Upstream docs: https://bitwarden.com/help/personal-api-key/

_{🔄 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/2245 **Author:** [@jjlin](https://github.com/jjlin) **Created:** 1/19/2022 **Status:** ✅ Merged **Merged:** 1/23/2022 **Merged by:** [@dani-garcia](https://github.com/dani-garcia) **Base:** `main` ← **Head:** `api-key` --- ### 📝 Commits (2) - [`69ee4a7`](https://github.com/dani-garcia/vaultwarden/commit/69ee4a70b453b81b96347fb299bf5c14f1038156) Add support for API keys - [`8f79007`](https://github.com/dani-garcia/vaultwarden/commit/8f7900759fdd2f2578461ac8aa38bbcd854a6b0f) Fix `scope` and `refresh_token` for API key logins ### 📊 Changes **14 files changed** (+182 additions, -17 deletions) <details> <summary>View changed files</summary> ➕ `migrations/mysql/2022-01-17-234911_add_api_key/down.sql` (+0 -0) ➕ `migrations/mysql/2022-01-17-234911_add_api_key/up.sql` (+2 -0) ➕ `migrations/postgresql/2022-01-17-234911_add_api_key/down.sql` (+0 -0) ➕ `migrations/postgresql/2022-01-17-234911_add_api_key/up.sql` (+2 -0) ➕ `migrations/sqlite/2022-01-17-234911_add_api_key/down.sql` (+0 -0) ➕ `migrations/sqlite/2022-01-17-234911_add_api_key/up.sql` (+2 -0) 📝 `src/api/core/accounts.rs` (+36 -3) 📝 `src/api/identity.rs` (+94 -11) 📝 `src/crypto.rs` (+28 -0) 📝 `src/db/models/device.rs` (+7 -2) 📝 `src/db/models/user.rs` (+8 -1) 📝 `src/db/schemas/mysql/schema.rs` (+1 -0) 📝 `src/db/schemas/postgresql/schema.rs` (+1 -0) 📝 `src/db/schemas/sqlite/schema.rs` (+1 -0) </details> ### 📄 Description This is mainly useful for CLI-based login automation. Upstream PR: https://github.com/bitwarden/server/pull/981 Upstream docs: https://bitwarden.com/help/personal-api-key/ --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>