Sign into Bitwarden with a passkey / "Login with passkeys" (for all BW apps)

Nail1684 · September 11, 2025, 8:32pm

… I just saw some movement here (but no idea of any timelines!):

github.com/bitwarden/clients

PM-13632: Enable sign in with passkeys in the browser extension

main ← anders/browser-prf

opened 07:32PM - 11 Sep 25 UTC

abergs

+118 -0

## 🎟️ Tracking https://bitwarden.atlassian.net/browse/PM-13632 ## 📔 Ob…jective This PR adds "Sign in with passkeys" UI to the browser extension. It's dependent on https://github.com/bitwarden/server/pull/6317 to work. ## 📸 Screenshots Demo video: https://share.cleanshot.com/93P7RsmJ <img width="410" height="621" alt="CleanShot 2025-09-11 at 21 36 45@2x" src="https://github.com/user-attachments/assets/d7bb789a-a6cd-4a94-823e-4b698382920e" /> <img width="410" height="621" alt="image" src="https://github.com/user-attachments/assets/9c74c18c-a925-4b70-9181-5917fa649e47" /> <img width="388" height="612" alt="image" src="https://github.com/user-attachments/assets/d4b88449-a7af-41c6-b8b8-c85f5a57e548" /> ## ⏰ Reminders before review - Contributor guidelines followed - All formatters and local linters executed and passed - Written new unit and / or integration tests where applicable - Protected functional changes with optionality (feature flags) - Used internationalization (i18n) for all UI strings - CI builds passed - Communicated to DevOps any deployment requirements - Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team ## 🦮 Reviewer guidelines - 👍 (`:+1:`) or similar for great changes - 📝 (`:memo:`) or ℹ️ (`:information_source:`) for notes or general info - ❓ (`:question:`) for questions - 🤔 (`:thinking:`) or 💭 (`:thought_balloon:`) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion - 🎨 (`:art:`) for suggestions / improvements - ❌ (`:x:`) or ⚠️ (`:warning:`) for more significant problems or concerns needing attention - 🌱 (`:seedling:`) or ♻️ (`:recycle:`) for future improvements or indications of technical debt - ⛏ (`:pick:`) for minor or nitpick changes

PS: … dependent on:

github.com/bitwarden/server

PM-13632: Add support for configuring multiple allowed origins

main ← anders/configurable-fido2-origins

opened 07:04PM - 11 Sep 25 UTC

abergs

+14 -1

## 🎟️ Tracking https://bitwarden.atlassian.net/browse/PM-13632 ## 📔 Ob…jective This PR contains enablement work for the browser extension work, tracked by https://bitwarden.atlassian.net/browse/PM-13632. It enables us to configure multiple allowed origins, so that we can list our domain (https://bitwarden.com etc) as well as our browser extension (chrome-extension://aabbbccc). It loads additional Origins from the configuraiton to allow us to update it dynamically or use different values in different environments. ## 📸 Screenshots ## ⏰ Reminders before review - Contributor guidelines followed - All formatters and local linters executed and passed - Written new unit and / or integration tests where applicable - Protected functional changes with optionality (feature flags) - Used internationalization (i18n) for all UI strings - CI builds passed - Communicated to DevOps any deployment requirements - Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team ## 🦮 Reviewer guidelines - 👍 (`:+1:`) or similar for great changes - 📝 (`:memo:`) or ℹ️ (`:information_source:`) for notes or general info - ❓ (`:question:`) for questions - 🤔 (`:thinking:`) or 💭 (`:thought_balloon:`) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion - 🎨 (`:art:`) for suggestions / improvements - ❌ (`:x:`) or ⚠️ (`:warning:`) for more significant problems or concerns needing attention - 🌱 (`:seedling:`) or ♻️ (`:recycle:`) for future improvements or indications of technical debt - ⛏ (`:pick:`) for minor or nitpick changes