Open
Bug 1832538
Opened 2 years ago
Updated 2 years ago
Security key devices are added as passkey on Google accounts.
Categories
(Core :: DOM: Web Authentication, defect, P3)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox114 | --- | affected |
People
(Reporter: mchiorean, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
5.32 MB,
image/gif
|
Details |
Found in
- 114.0b2 (20230321175953)
Affected versions
- 114.0b2
Tested platforms
- Affected platforms: Win10, Win7, Ubuntu 20.04, Mac 12.6
- Unaffected platforms: -
Steps to reproduce
- Log in with a google account. Make sure you have a Google account with second authentication enabled.
- On google select 'Manage your Google Account' and Security from the left side menu..
- Press on Security key button, then press on Add security key.
- Press on Proceed button.
- Enter correct PIN and press on Sign in.
- Enter the 'Security key name' and follow the instructions to add the security device.
- Check Security page of Google account and the security key device.
Expected result
- Security key should be correctly added.
Actual result
- Passley is added instead of security key.
Additional notes
- This seems to be a Google issue, but we logged this only for tracking purposes .
Regression range
- Not a regression as this is newly implemented.
Reporter | ||
Updated•2 years ago
|
Has STR: --- → yes
status-firefox114:
--- → affected
Comment 1•2 years ago
|
||
:mchiorean, if you think that's a regression, could you try to find a regression range using for example mozregression?
Reporter | ||
Comment 2•2 years ago
|
||
Attached short demo of the issue.
Reporter | ||
Updated•2 years ago
|
Updated•2 years ago
|
Severity: -- → S3
Priority: -- → P3
Comment 3•2 years ago
|
||
I've observed this issue with Chrome/Edge as well, I don't believe this is a Firefox problem.
You need to log in
before you can comment on or make changes to this bug.
Description
•