github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-09 11:44:41 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

iOS - When Vault Timeout Action is set to Log out and 2FA is configured, Auto-fill prompt does not read NFC YubiKey. #1154

New Issue
Closed
opened 2025-11-26 22:40:36 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-26 22:40:36 -06:00
Owner
Copy Link

Originally created by @SergeantConfused on GitHub (Dec 15, 2020).

Describe the Bug

When you set the Vault Timeout Action to Log out, and you have 2FA using a YubiKey OTP Security Key configured:
When you click on 'Passwords' at the top of the keyboard to auto-fill your credentials, the 2FA authentication step does not read the YubiKey 5C NFC, it does not display the 'Ready to Scan' prompt. Holding the YubiKey to the NFC scanner would display a banner for Yubico's website.

Steps To Reproduce

  1. Set your Vault Timeout Action to Log out.
  2. Set the Vault Timeout to 1 Minute.
  3. Go to http://vault.bitwarden.com/
  4. Tap a credential field and then tap on 'Passwords'.
  5. Enter your email address and master password.

Expected Result

Bitwarden would read the NFC YubiKey and log in.

Actual Result

Bitwarden does not prompt to scan the NFC YubiKey and you cannot log in.

Screenshots or Videos

N/A.

Environment

  • Device: iPhone SE 2020.
  • Operating system: iOS 14.2.
  • Build Version: 2.7.0 (358).
  • Is this a Beta release? N.

Additional Context

Please note that you can log in by using a YubiKey 5Ci. You can tap the YubiKey TOTP field and then tap the YubiKey 5Ci while it's connected to the Lightning port.

Originally created by @SergeantConfused on GitHub (Dec 15, 2020). ## Describe the Bug When you set the Vault Timeout Action to Log out, and you have 2FA using a YubiKey OTP Security Key configured: When you click on 'Passwords' at the top of the keyboard to auto-fill your credentials, the 2FA authentication step does not read the YubiKey 5C NFC, it does not display the 'Ready to Scan' prompt. Holding the YubiKey to the NFC scanner would display a banner for Yubico's website. ## Steps To Reproduce 1. Set your Vault Timeout Action to Log out. 2. Set the Vault Timeout to 1 Minute. 3. Go to http://vault.bitwarden.com/ 4. Tap a credential field and then tap on 'Passwords'. 5. Enter your email address and master password. ## Expected Result Bitwarden would read the NFC YubiKey and log in. ## Actual Result Bitwarden does not prompt to scan the NFC YubiKey and you cannot log in. ## Screenshots or Videos N/A. ## Environment - Device: iPhone SE 2020. - Operating system: iOS 14.2. - Build Version: 2.7.0 (358). - Is this a Beta release? N. ## Additional Context Please note that you can log in by using a YubiKey 5Ci. You can tap the YubiKey TOTP field and then tap the YubiKey 5Ci while it's connected to the Lightning port.
GiteaMirror commented 2025-11-26 22:40:37 -06:00
Author
Owner
Copy Link

@heipra commented on GitHub (Feb 2, 2021):

I've been experiencing the same issue on iOS 14.4. in Build Version 2.8.0 (449).

@heipra commented on GitHub (Feb 2, 2021): I've been experiencing the same issue on iOS 14.4. in Build Version 2.8.0 (449).
GiteaMirror commented 2025-11-26 22:40:37 -06:00
Author
Owner
Copy Link

@SergeantConfused commented on GitHub (Mar 14, 2021):

This is caused by a limitation within the operating system that prevents using NFC in the autofill flow and we cannot change that. This means that it would not be possible to use autofill on iOS if the 'Vault Timeout Action' is set to 'Log out' and the only 2FA method requires NFC.

@SergeantConfused commented on GitHub (Mar 14, 2021): This is caused by a limitation within the operating system that prevents using NFC in the autofill flow and we cannot change that. This means that it would not be possible to use autofill on iOS if the 'Vault Timeout Action' is set to 'Log out' and the only 2FA method requires NFC.
GiteaMirror commented 2025-11-26 22:40:38 -06:00
Author
Owner
Copy Link

@vvolkgang commented on GitHub (Jun 20, 2024):

Issue migrated to https://github.com/bitwarden/mobile/issues/1178

@vvolkgang commented on GitHub (Jun 20, 2024): Issue migrated to https://github.com/bitwarden/mobile/issues/1178
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#1154
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?