/SOLVED ( see in feedback )

I'm experiencing what seems to be a WebAuthn/Passkey situation on Binance and want to know if anybody can reproduce it.

Surroundings

• OS: Linux Mint 22.three
• YubiKey: YubiKey 5 NFC
• Firmware: 5.7.4
• Browsers examined:
  • Brave 1.92.143 (Chromium 150.0.7871.182)
  • Chromium 150.0.7871.124
• Both browsers produce the exact same conduct.

Steps to reproduce

1. Log in to Binance.
2. Go to Safety → Passkeys / Safety Keys.
3. Add a brand new safety key using the YubiKey.
4. The browser:
   • asks for the YubiKey FIDO2 PIN,
   • then the YubiKey LED begins blinking,
   • I touch the safety key,
   • Binance reviews that the important thing has been efficiently added.
5. Binance instantly sends the confirmation e mail saying that a new passkey/security key has been added.

The whole lot seems to complete successfully.

Drawback

After logging out:

1. I enter my e-mail tackle.
2. I click on Proceed with passkey.
3. The browser once more asks for the YubiKey PIN.
4. The YubiKey LED blinks.
5. I contact the important thing.
6. The browser returns:

Authentication all the time fails.

Further observations

• Binance shows the registered credential as:

  Safety Key on Linux Cross System

which appears unusual for a USB YubiKey.

• Deleting the registered key from Binance also requires getting into the YubiKey PIN and touching the important thing, so Binance clearly recognizes the YubiKey throughout delicate operations.

YubiKey verification

FIDO2 is enabled and dealing usually.

ykman information:

Gadget sort: YubiKey 5 NFC Firmware version: 5.7.four FIDO2: Enabled 

Resident credentials saved on the important thing:

google.com login.microsoft.com reddit.com 

No Binance credential is listed.

Different web sites (Google, Microsoft, Reddit) work appropriately with the identical YubiKey.

What I've already examined

• Eliminated and recreated the important thing multiple occasions.
• Tried with the important thing already inserted and inserted in the course of the course of.
• Examined with both Courageous and Chromium.
• Similar end result each time.

Query

Has anybody else on Linux skilled this?

Might this be a Binance WebAuthn problem (credential creation not completing appropriately or RP ID mismatch), or is there a recognized compatibility problem with Linux browsers and Binance passkeys?

Any insight from the Binance group or customers who have successfully configured a YubiKey on Linux can be significantly appreciated.

/SOLVED ( see in comments )