bitwarden / bitwarden/clients

Bitwarden doesn't recognize it has a passkey to offer to LinkedIn.com

Open
#7,545 40 comments 7 reactions 0 assignees View on GitHub
browser bug
Dominant language
TypeScript
Stars
13.8k
Forks
2k
Avg merge
3d 9h
Merged PRs (30d)
397

Description

### Steps To Reproduce

This was discovered when I was testing if #7302 was resolved. That issue is not occurring, but there is a new issue.

1. Logging in to LinkedIn.com using username/password, I went to "Settings" and "Sign in & Security" and created a passkey in Bitwarden (I am using the passkey saved as part of finding #7302 )
2. I verified Bitwarden shows a passkey stored for linkedin.com
3. Log out of LinkedIn
4. Go to LinkedIn login page: https://www.linkedin.com/login
5. Click "Sign in with a passkey"

### Expected Result

Bitwarden offers to serve up the saved passkey for login

### Actual Result

Bitwarden popup says "No passkeys found for this application"

### Screenshots or Videos

At the signin page, prior to logging in, Bitwarden recognizes I have a vault entry for LinkedIn. Clicking the BW icon shows this:
image

Viewing the entry, I confirm a passkey is saved:
image

This is the sign-in page:
image

This is the popup when "Sign in with a passkey" is clicked
image

### Additional Context

_No response_

### Operating System

Windows

### Operating System Version

10.0.19045 Build 19045

### Web Browser

Chrome

### Browser Version

120.0.6099.200 (Official Build) (64-bit)

### Build Version

2024.1.0

### 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

Open the contributing guide

Research direction

Reproduce the issue on Windows 10 in Chrome 120 using the LinkedIn login flow described above, then trace the browser extension's passkey offering path. Done means Bitwarden recognizes the saved linkedin.com passkey and offers it when "Sign in with a passkey" is selected.

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
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.