chase.com not utilizing passkey from Extension or Desktop Client
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 2k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 397
Description
### Steps To Reproduce
1. Go to auth.chase.com
2. Click on Passwordless sign-in
3. It should prompt for a passkey from Bitwarden.
### Expected Result
It should prompt for a passkey from Bitwarden.
### Actual Result
It prompts for a passkey from Windows, Bitwarden is not an option.
### Screenshots or Videos
### Additional Context
I've tried on both Vivaldi and Edge (Desktop).
### Operating System
Windows
### Operating System Version
Windows 10 Pro N 22H2 19045.6466
### Web Browser
Vivaldi
### Browser Version
7.9.3970.50 (Official Build) (64-bit) , Chromium 146.0.7680.189
### Environment Versions
Version: 2026.3.0
SDK: main (7637fdf)
Server version: 2025.12.0 (Vaultwarden)
### Issue Tracking Info
- [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Contributor guide
Research direction
Start by reproducing the flow at auth.chase.com on Windows using the Bitwarden extension and Desktop Client, as described in the reproduction steps. Compare the passkey choices shown after selecting Passwordless sign-in; done means Bitwarden is offered as a passkey option rather than only Windows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100