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
On a Yubikey Security Key, set a pin using the Yubikey Manager and configure the key to always prompt for the pin. You can do so by running this command in the terminal: ykman fido config toggle-always-uv
Add the Yubikey Security Key as a Passkey / WebAuthn option in your Bitwarden account
Set your Bitwarden account to require MFA on Login
Install the Bitwarden iOS app
Sign-in to it using your master password
When prompted for MFA, select 'Launch WebAuthn' and select 'Security Key'
Bring the Yubikey Security close to the iPhone
When recognized, enter the pin for your Yubikey
Expected Result
It should have proceeded to login into and unlock my vault
Actual Result
I get stuck in a loop where it just continues to ask for my Security Key
Screenshots or Videos
No response
Additional Context
The Yubikey, when configured this way, works fine with Bitwarden on desktop in various web browsers, like Safari, Firefox, and Brave
Build Version
2024.12.0 (1740)
What server are you connecting to?
US
Self-host Server Version
No response
Environment Details
No response
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:
Steps To Reproduce
ykman fido config toggle-always-uv
Expected Result
It should have proceeded to login into and unlock my vault
Actual Result
I get stuck in a loop where it just continues to ask for my Security Key
Screenshots or Videos
No response
Additional Context
The Yubikey, when configured this way, works fine with Bitwarden on desktop in various web browsers, like Safari, Firefox, and Brave
Build Version
2024.12.0 (1740)
What server are you connecting to?
US
Self-host Server Version
No response
Environment Details
No response
Issue Tracking Info
The text was updated successfully, but these errors were encountered: