Jump to content

FIDO/U2F Two Factor Authentication


Adam
 Share

Recommended Posts

Does anyone use a Yubikey with Safari or NFC on iOS?

Something must have been changed with the latest Safari 17.4 or iOS Update. When I try to log-in using macOS Safari or NFC on iOS Safari/iOS Chrome, there is no longer an option to select Security keys. Whereas the Security key option still shows up on Google Sign or GitHub.

Security key shows up on GitHub:

image.png.e2b93188d31830d3e79e99f3ca066891.png


Security key option is missing on a PW site using the WebAuthn two-factor authentication module.

image.png.5a8f6c3f23153576b1d0112e83074824.png

Link to comment
Share on other sites

  • 1 month later...
On 5/19/2024 at 4:29 PM, howdytom said:

Anyone?

I am no longer able to login via iOS using a Yubikey.

Sorry fr the late reply on this one. I assumed for the first reply it was the U2F module which is no longer used.

I have just setup a new PW install and was able to use my security key on my iPhone.  I am using firefox though. I want to suggest its because of passkeys being a thing now but I have that option too?

Can you confirm PW version, IOS version, Browser on IOS
Have you tested on a blank install? Might need to disable and reenable the webauthn for users?

Link to comment
Share on other sites

AP1GczNUJeOH6q1UDC4iQPD8YBYi2FYpzVYGN1_Za16RjLU2_qVzJGBwkFzJfIFh3LquLpF3vnDyaFpNP0Q-GqCVGu82VEu6L9fg97dX99bZ7LkS9mfSPnfn0eH_d4hLEOqVFOLMF3LE-BXu3CpjOYEGIze4J0Sydm6g3rFVC4hkUGOk4032R9NGXInw4p0LWX1VcfiWw1Xfk2zQXYX715Hz7eKbS_t4MiDFVvJ9Hks0yF9QR9K6FjUWFEtD8_LiU0aV0SdDer9__E02OoIlkuvpm2gfmIjW3LfjbWPEGRDbeEQUZjuLJAFWfRKb8cEiXxexCXK5afBqusUqlOe5D_oRaX5HvvPzgLh5Xmfze_Cx7KY8RaBRBRtdFBZASR6uNXK48NSm35u7bQAArbckmQHZaWR07tKdB7SNzId8N7CXpYZuCtQoRat3G5RtuH5Ym4QG1Hqi1D74eXPftwuDTalkKq3rifzEIkhncOYL5bg9wwR1mkLkJdr390Jjl5jNQ76KPwCWKgV6-hJxWkvt9muRfm_WhlYLn5YIAm9PRIHubtXcnUC27YSWPs-5ZzyERdyWaXkR_Kn99SwqcLyo2e4KUO2mPK_z7dsDgYPgKaPHb4BsgIjQjcBOZZSk2TkzbJuDwdlphyufnw1C1WQAZZJzBrtabizRoRTgAX0yETt88GoplegmiDzjTogZRVS0nbMnXdqaESJmGuN86A5ilY3Rg1uwqBSgoSjLg8NtYX8nUWSWzMGCUGZzGoN3ociflGCIIW-BqLjjPjsZyDLvxwrbUH8aTRMm2jUguAFg4yv_9D1M_UMBWg-8iPR0qAqy8ib9T68MCI7WRmdgWcIi28WpUz_Paacd_ZCdQyCl8EvMKRWHVxRgfncIS4Vo_NHKnm249zB-bbUj5qsgD4ypiyAY9fkLkrAe=w441-h955-s-no?authuser=0

I dont have a Mac for testing I am afraid so this bug is limited for me. I imagine the issue will be in the JS file if there is a problem. and might take a bit of unwrapping as been a while since I made this.

Link to comment
Share on other sites

Okay https://denniskniep.github.io/posts/02-fragile-passkey-ecosystem-for-enterprises/#security-key-can-not-be-selected---due-to-transport-selection

Found that link. suggests iOS 17.4 and whatever MacOS is now is just stupid in like 500 ways urgh.

A temporary solution might be editing line 30~ of the module file to disable BLE security keys. that way we arent offering all types... Why that is a problem for apple I have no clue.

I will be updating the library anyway but let me know if that works at all if so I will make that a full on change as I doubt BLE keys are used much in 2024

  • Thanks 1
Link to comment
Share on other sites

@Adam Thanks for getting back. This issue seems to be related to iOS 17.4 and macOS Safari 17.4.1. The issue occurred with iOS Safari, iOS Chrome, iOS Firefox running iOS 17.4 and with macOS Safari 17.4.1

Solution: 
In the meantime I have updated to iOS 17.5, which resolves the login issue and the Security key option is visible again. I did not disable or reenable the Webauthn. I have tested it with 5 ProcessWire 3.0.229 sites. I am glad it is working again. This has been a serious bug.

Thanks for keeping the module alive.

Link to comment
Share on other sites

@howdytom Ok I none of my IOS devices have 17.4 exactly so that is probably why I could not replicate that.

I had a quick go at updating the dependency but everything breaks when I do that. I have no idea what has changed in 2 years but its enough to cause challenge issues adding new keys and existing keys are no longer "familiar" on the login prompt. Simply put I do not have enough knowledge or time to dedicate to this besides quick bug fixes.

A quick glance at the github changes between 1.1.3 and 2.0.0 really does not show why it falls apart after an update. As its failing even the registration part which is unrelated to the changes

I am surprised no one has made a better webauthn for processwire. This was and still is a proof of concept. It works but very much could do with someone that is good at PHP

The initial login bug also is not happening for me with a fresh copy of PW and module in Chrome 125. Sounds strange though. I would be happy to look into that but its hard to debug when the issue does not happen for me. Is this also on MacOS? do you get the system prompts as expected??

  • Like 1
Link to comment
Share on other sites


@AdamYeah, it explains why Webauthn and Yubikeys remain a niche product. It is a pity. I really appreciate taking the time for checking. My second question regarding initial login bug can be ignored. It is a minor browser specific bug.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...