github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-07 19:39:41 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #679] iPhone App: YubiKey 2FA login challenge not designed for YubiKey 5Ci #48979

New Issue
Closed
opened 2026-05-01 07:31:12 -05:00 by GiteaMirror · 8 comments
GiteaMirror commented 2026-05-01 07:31:12 -05:00
Owner
Copy Link

Originally created by @Ayitaka on GitHub (Dec 25, 2019).
Original GitHub issue: https://github.com/bitwarden/android/issues/679

  • iPhone 8 Plus
  • iOS 13.3
  • Latest Bitwarden App
  • "One of my keys supports NFC" is unchecked in the YubiKey OTP section.

When the Bitwarden iPhone app asks for your YubiKey it appears that it was originally designed for the YubiKey NEO with NFC. It should be updated to include wording for, and activation by, the YubiKey 5Ci via the lightning port.

First, the wording:

To continue, hold your YubiKey NEO against the back of the device.

Now that you can also use the YubiKey 5Ci via the lightning port, this wording should be changed to something generic or to include the YubiKey 5Ci and how to activate it (Currently: Plug YubiKey into lightning port, tap Cancel, tap the text field, and then press buttons on side of YubiKey).

Second, the text field:
The way the current Bitwarden app works, to use the 5Ci you must first tap Cancel to stop the "Ready to Scan" popup window and then tap the (black on black background) text field immediately above the "Remember me" area. That text field is not at all obvious or intuitive, as you can see from Screenshot 2 below. At the very least, making that text field contrast against the black background might be necessary.

Ideally though, the whole process/popup should be changed from "Ready to Scan" to "Waiting for YubiKey", and to handle input from the 5Ci via lightning port (and USB-C for Android?) the same way it does for the NEO via NFC by automatically selecting the text field/placing the resulting key into the text field.

Thanks!

Screenshot 1 - Ready to Scan

image0

Screenshot 2 - What text field?

image1

Originally created by @Ayitaka on GitHub (Dec 25, 2019). Original GitHub issue: https://github.com/bitwarden/android/issues/679 - iPhone 8 Plus - iOS 13.3 - Latest Bitwarden App - "One of my keys supports NFC" is unchecked in the YubiKey OTP section. When the Bitwarden iPhone app asks for your YubiKey it appears that it was originally designed for the YubiKey NEO with NFC. It should be updated to include wording for, and activation by, the YubiKey 5Ci via the lightning port. **First, the wording**: > To continue, hold your YubiKey NEO against the back of the device. Now that you can also use the YubiKey 5Ci via the lightning port, this wording should be changed to something generic or to include the YubiKey 5Ci and how to activate it (Currently: Plug YubiKey into lightning port, tap Cancel, tap the text field, and then press buttons on side of YubiKey). **Second, the text field**: The way the current Bitwarden app works, to use the 5Ci you must first tap Cancel to stop the "Ready to Scan" popup window and then tap the (black on black background) text field immediately above the "Remember me" area. That text field is not at all obvious or intuitive, as you can see from Screenshot 2 below. At the very least, making that text field contrast against the black background might be necessary. Ideally though, the whole process/popup should be changed from "Ready to Scan" to "Waiting for YubiKey", and to handle input from the 5Ci via lightning port (and USB-C for Android?) the same way it does for the NEO via NFC by automatically selecting the text field/placing the resulting key into the text field. Thanks! <details> <summary>Screenshot 1 - Ready to Scan</summary> ![image0](https://user-images.githubusercontent.com/22988712/71438595-3fcec500-26ab-11ea-91d3-f3afa2068a2c.png) </details> <details> <summary>Screenshot 2 - What text field?</summary> ![image1](https://user-images.githubusercontent.com/22988712/71438604-452c0f80-26ab-11ea-8b7b-f3528fe18a3a.png) </details>
GiteaMirror commented 2026-05-01 07:31:15 -05:00
Author
Owner
Copy Link

@jrsmiley commented on GitHub (Jan 9, 2020):

I'm glad I read this. I have used 5ci on the iPad version of Bitwarden in the past and it worked fine. Trying again today, it appeared not to be working. What I was missing was necessity of clicking on the invisible (black on black) text field before touching the 5ci. Works fine. Agree this UI error needs to be fixed.

<!-- gh-comment-id:572392405 --> @jrsmiley commented on GitHub (Jan 9, 2020): I'm glad I read this. I have used 5ci on the iPad version of Bitwarden in the past and it worked fine. Trying again today, it appeared not to be working. What I was missing was necessity of clicking on the invisible (black on black) text field before touching the 5ci. Works fine. Agree this UI error needs to be fixed.
GiteaMirror commented 2026-05-01 07:31:17 -05:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 14, 2021):

I just ran into this and I also nominated a feature request on the Forums ... This is a little glitchy. Thanks @jrsmiley and @Ayitaka for figuring this out.

<!-- gh-comment-id:880052450 --> @ghost commented on GitHub (Jul 14, 2021): I just ran into this and I also nominated a feature request on the Forums ... This is a little glitchy. Thanks @jrsmiley and @Ayitaka for figuring this out.
GiteaMirror commented 2026-05-01 07:31:18 -05:00
Author
Owner
Copy Link

@Nephilimi commented on GitHub (Jan 29, 2022):

If you have a Yubikey NEO and encounter this on an iPad this experience is especially bad for a new user.

First issue; per Ayitaka comment back in 2019 Bitwarden does support the USB/Lightning hardwired keyboard key input method. Current picture and instructions do not mention that.

Next issue; the text input field where you can select and have the Yubikey as keyboard fill in the key is invisible.
yubikeyiPad

I would suggest the instructions and picture shown on that page be updated to include the hardwired connection the Yubikey 5Ci and NEO (iPad) support. Also if the text input filed can be called out somehow that would help tremendously. Thank you.

<!-- gh-comment-id:1024977505 --> @Nephilimi commented on GitHub (Jan 29, 2022): If you have a Yubikey NEO and encounter this on an iPad this experience is especially bad for a new user. **First issue**; per Ayitaka comment back in 2019 Bitwarden does support the USB/Lightning hardwired keyboard key input method. Current picture and instructions do not mention that. **Next issue**; the [text input field where you can select and have the Yubikey as keyboard fill in the key is invisible](https://i.imgur.com/ayM2bM6.jpg). ![yubikeyiPad](https://user-images.githubusercontent.com/26043969/151675889-04a36aed-3df5-4f86-8b28-c64f0b6d8689.jpg) I would suggest the instructions and picture shown on that page be updated to include the hardwired connection the Yubikey 5Ci and NEO (iPad) support. Also if the text input filed can be called out somehow that would help tremendously. Thank you.
GiteaMirror commented 2026-05-01 07:31:19 -05:00
Author
Owner
Copy Link

@Nephilimi commented on GitHub (Sep 6, 2023):

This is still broken in 2023 on ios 17...

IMG_0316

<!-- gh-comment-id:1707465959 --> @Nephilimi commented on GitHub (Sep 6, 2023): This is still broken in 2023 on ios 17... ![IMG_0316](https://github.com/bitwarden/mobile/assets/26043969/051476a6-4136-4878-8b68-4d07bd1c0f1e)
GiteaMirror commented 2026-05-01 07:31:20 -05:00
Author
Owner
Copy Link

@dirk-bester commented on GitHub (Sep 23, 2023):

Finally "solved" this on iPad. The challenge dialog with the dumb NFC picture after you now chose "no NFC" when setting up YubiKey is ... scrollable. So:

  • Wipe all your Yubikeys in the web app
  • Uncheck "I use insecure NFC keys"
  • Register your 5ci and USB-C Yubikeys
  • Kill the iPad app and sign in again (swipe up from bottom edge to get to desktop, again to see running apps, flick bitwarden up to kill it)
  • When you see the "tap the NFC key I don't have" picture, scroll down to reveal the button to press to instead use your 5ci or 5c.

I cannot wait till Passkey sign in and this nonsense goes away in October or whatever. I just typed in my 50+ character password over 20 times this round of trying to get it to work. Annoying.

<!-- gh-comment-id:1732335088 --> @dirk-bester commented on GitHub (Sep 23, 2023): Finally "solved" this on iPad. The challenge dialog with the dumb NFC picture after you now chose "no NFC" when setting up YubiKey is ... scrollable. So: - Wipe all your Yubikeys in the web app - Uncheck "I use insecure NFC keys" - Register your 5ci and USB-C Yubikeys - Kill the iPad app and sign in again (swipe up from bottom edge to get to desktop, again to see running apps, flick bitwarden up to kill it) - When you see the "tap the NFC key I don't have" picture, scroll down to reveal the button to press to instead use your 5ci or 5c. I cannot wait till Passkey sign in and this nonsense goes away in October or whatever. I just typed in my 50+ character password over 20 times this round of trying to get it to work. Annoying.
GiteaMirror commented 2026-05-01 07:31:24 -05:00
Author
Owner
Copy Link

@Nephilimi commented on GitHub (Sep 23, 2023):

Finally "solved" this on iPad. The challenge dialog with the dumb NFC picture after you now chose "no NFC" when setting up YubiKey is ... scrollable. So:

  • Wipe all your Yubikeys in the web app
  • Uncheck "I use insecure NFC keys"
  • Register your 5ci and USB-C Yubikeys
  • Kill the iPad app and sign in again (swipe up from bottom edge to get to desktop, again to see running apps, flick bitwarden up to kill it)
  • When you see the "tap the NFC key I don't have" picture, scroll down to reveal the button to press to instead use your 5ci or 5c.

I cannot wait till Passkey sign in and this nonsense goes away in October or whatever. I just typed in my 50+ character password over 20 times this round of trying to get it to work. Annoying.

You might want to check out this issue I posted; https://github.com/bitwarden/mobile/issues/2745

<!-- gh-comment-id:1732339092 --> @Nephilimi commented on GitHub (Sep 23, 2023): > Finally "solved" this on iPad. The challenge dialog with the dumb NFC picture after you now chose "no NFC" when setting up YubiKey is ... scrollable. So: > > * Wipe all your Yubikeys in the web app > * Uncheck "I use insecure NFC keys" > * Register your 5ci and USB-C Yubikeys > * Kill the iPad app and sign in again (swipe up from bottom edge to get to desktop, again to see running apps, flick bitwarden up to kill it) > * When you see the "tap the NFC key I don't have" picture, scroll down to reveal the button to press to instead use your 5ci or 5c. > > I cannot wait till Passkey sign in and this nonsense goes away in October or whatever. I just typed in my 50+ character password over 20 times this round of trying to get it to work. Annoying. You might want to check out this issue I posted; https://github.com/bitwarden/mobile/issues/2745
GiteaMirror commented 2026-05-01 07:31:26 -05:00
Author
Owner
Copy Link

@dirk-bester commented on GitHub (Sep 23, 2023):

Finally "solved" this on iPad. The challenge dialog with the dumb NFC picture after you now chose "no NFC" when setting up YubiKey is ... scrollable. So:

  • Wipe all your Yubikeys in the web app
  • Uncheck "I use insecure NFC keys"
  • Register your 5ci and USB-C Yubikeys
  • Kill the iPad app and sign in again (swipe up from bottom edge to get to desktop, again to see running apps, flick bitwarden up to kill it)
  • When you see the "tap the NFC key I don't have" picture, scroll down to reveal the button to press to instead use your 5ci or 5c.

I cannot wait till Passkey sign in and this nonsense goes away in October or whatever. I just typed in my 50+ character password over 20 times this round of trying to get it to work. Annoying.

You might want to check out this issue I posted; #2745

I just go by what google serves up.

However, you are right that if I find the particular place to search for each product it could be more efficient than hoping the algorithm does a good job. Today I cared again because copy paste from new iPhone to iPad is not working because reasons which broke my workaround for the NFC plague.

<!-- gh-comment-id:1732348044 --> @dirk-bester commented on GitHub (Sep 23, 2023): > > Finally "solved" this on iPad. The challenge dialog with the dumb NFC picture after you now chose "no NFC" when setting up YubiKey is ... scrollable. So: > > > > * Wipe all your Yubikeys in the web app > > * Uncheck "I use insecure NFC keys" > > * Register your 5ci and USB-C Yubikeys > > * Kill the iPad app and sign in again (swipe up from bottom edge to get to desktop, again to see running apps, flick bitwarden up to kill it) > > * When you see the "tap the NFC key I don't have" picture, scroll down to reveal the button to press to instead use your 5ci or 5c. > > > > I cannot wait till Passkey sign in and this nonsense goes away in October or whatever. I just typed in my 50+ character password over 20 times this round of trying to get it to work. Annoying. > > You might want to check out this issue I posted; #2745 I just go by what google serves up. However, you are right that if I find the particular place to search for each product it could be more efficient than hoping the algorithm does a good job. Today I cared again because copy paste from new iPhone to iPad is not working because reasons which broke my workaround for the NFC plague.
GiteaMirror commented 2026-05-01 07:31:28 -05:00
Author
Owner
Copy Link

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

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

<!-- gh-comment-id:2181550286 --> @vvolkgang commented on GitHub (Jun 20, 2024): Issue migrated to https://github.com/bitwarden/mobile/issues/679
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#48979
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?