You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Go to a passkey supported login page (e.g. Amazon)
Use the passkey authentication method
Expected Result
The TOTP should be in the clipboard.
Actual Result
The TOTP is not in the clipboard when using the passkey, but only when using password login methods.
Screenshots or Videos
No response
Additional Context
No response
Operating System
Windows
Operating System Version
No response
Web Browser
Brave
Browser Version
No response
Build Version
1.70.119
Issue Tracking Info
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.
The text was updated successfully, but these errors were encountered:
Your issue appears to be describing the intended behavior of the software. If you want this to be changed, it would be a feature request.
We use GitHub issues as a place to track bugs and other development-related issues. The Bitwarden Community Forums has a Feature Requests section for submitting, voting for, and discussing requests like this one: https://community.bitwarden.com/c/feature-requests/
Please sign up on our forums (https://community.bitwarden.com/signup) and search to see if this request already exists. If so, you can vote for it and contribute to any discussions about it. If not, you can re-create the request there so that it can be properly tracked.
Steps To Reproduce
Expected Result
The TOTP should be in the clipboard.
Actual Result
The TOTP is not in the clipboard when using the passkey, but only when using password login methods.
Screenshots or Videos
No response
Additional Context
No response
Operating System
Windows
Operating System Version
No response
Web Browser
Brave
Browser Version
No response
Build Version
1.70.119
Issue Tracking Info
The text was updated successfully, but these errors were encountered: