Not really a bug, its expected behavior as you would need a portable passkey app, Proton pass for example.
XenForo 2.3 bugs, problems, and new stuff thread!
- Thread starter kindai
- Start date
Not really a bug, its expected behavior as you would need a portable passkey app, Proton pass for example.
Slightly off-topic but does Bitwarden do this as well?
Man of Honour
Yes multiple passkey handlers are on the phone but the forum only seems to request a passkey from Google, not any of the others. For example I have Samsung Pass, Firefox (which is the default handler for passwords/passkeys as everything of mine is synchronised via it), Microsoft Authenticator as well as Google's own app, yet the forum only requests the passkey just created from Google which it doesn't find because of the above.
It also won't create a passkey to the others even though it generates a passkey regardless of which handler is manually set as default in Android and only requests one from google upon logging out then back in.
So for now Passkeys only work on the desktop which is fine, doesn't work on mobile but can log in using just password without 2FAing with a passkey, which is also fine for now.
Last edited:
Works on both, you likely need to go into your phone settings and specify which Passkey handler to use (otherwise it will default to Google).
Man of Honour
I only posted after doing all this due diligence. The issue does not exist on anything else, only on this forum.
The "Featured content" banner is (I think) in the same place "New posts" used to be. I keep pressing it by accident when meaning to browse new posts, but I guess that will pass in a few days.
What is the intended function of this section/filter?
rp2000
What is the intended function of this section/filter?
rp2000
Man of Honour
I've figured out what's going on, the wording/implementation needs work to be clear on how this is supposed to work and what a user needs to do as it will be confusing for many no doubt for those who access the forums across multiple devices.
The correct process as I discovered is like so, you don't actually even have to click the sign in via passkey button to log in, just enter your saved password and click log in, as long as a passkey was generated previously on the phone/desktop etc, you will immediately log in just like you could before enforced 2FA became a thing.
Now on phone or desktop, since I generated a passkey (it's stored somewhere, who knows where on phone as it's not Google), it detects that a device passkey exists when logging in with the normal password and gets you in. If a device passkey doesn't exist then you can only log in with a backup code which a bunch are generated when you first enable passkeys and the 2FA screen gets enabled in during that process. NOTE THOSE BACKUP CODES DOWN. If you disable app based code 2FA and only use Passkeys, then new backup codes are generated too so your old ones are useless. Note them down!
So now with passkeys, no monthly signing in again with a 2FA code, as the passkey 2FAs you behind the scenes.
Cool.
Last edited:
This is where I'm (still) seeing it:Removed itWe dont have any Featured content as of yet.
rp2000
Soldato
CHANGE BAD
Srsly though, when long-pressing the like button on Android, the reaction options pop up fast then I get a long press/context menu (browser right click effectively).
Samsung Galaxy S9, Chrome, Android 10.
Srsly though, when long-pressing the like button on Android, the reaction options pop up fast then I get a long press/context menu (browser right click effectively).
Samsung Galaxy S9, Chrome, Android 10.
Last edited:
Zap
Man of Honour
Can I be the first to say that it's fully Groce™
I can say this after an extensive test which included clicking new posts once, and then clicking this thread.
I can say this after an extensive test which included clicking new posts once, and then clicking this thread.
Commissario
Man of Honour
Yeah once I sussed what was going on it works fine, as per my last comment above. With this you don't need to do anything other than the initial creation of the Passkey for that device. That's it. After this point just log in like you would have done before the whole 2FA thing was added to the forums. The Passkey gets recognised behind the scenes and you are in without having to load any passkey app.
On Windows 11 I just enter my Windows login PIN which handles all device level passkeys like when I log into Windows and other stuff. Again super convenient.
On Windows 11 I just enter my Windows login PIN which handles all device level passkeys like when I log into Windows and other stuff. Again super convenient.
Caporegime
The scrolling is really janky. Quite a few times it will go nuts.
Here’s a GIF I captured. Keep in mind this is low FPS, in reality it’s very fast and trippy.
iPhone 15 using Safari.
Here’s a GIF I captured. Keep in mind this is low FPS, in reality it’s very fast and trippy.
iPhone 15 using Safari.
Soldato
Here's a bug, if you disable 2FA and use Passkeys, then this works fine on desktop, but if you the go to mobile via the phone web browser (also Firefox though not relevant) then you can add a passkey for that device and it saves fine and shows in the list of passkeys, but when you go to log in via mobile web browser it tries to use Google to find the passkey which obviously doesn't exist
Also once passkeys are enabled, you can't then go in and re-enable any other 2FA as the toggle switch doesn't do anything.
Works for me... When I setup my passkey on the desktop, it asked me where I wanted it saved and I chose my phone... When I logged out on desktop and then logged back in (to test it), it gave me the option to login with a Passkey... When I hit the button, it sent a notification to my phone which I then unlocked, confirmed it was me using fingerprint id and my desktop got authorised to log in.
Last edited:
Man of Honour
It's all sorted, see above! Seems with firefox mobile the passkey is auto utilised directly and behind the scenes. No need to press anything other than login at the username/password screen which is autofilled in anyway.
Must be Safari related on how it handles whatever API is being used by the update I guess. On Firefox it's buttery smooth.The scrolling is really janky. Quite a few times it will go nuts.
Here’s a GIF I captured. Keep in mind this is low FPS, in reality it’s very fast and trippy.
iPhone 15 using Safari.
Last edited:
