I’m experiencing a Daybreak hardware security key recognition issue with two TrustKey T110 devices.
Both devices are physical FIDO2/U2F security keys. I enrolled them through the explicit “Security key” option in the Windows/WebAuthn prompt, entered the FIDO2 PIN, and physically touched each key to complete enrollment.
Both keys work for authentication, but in ChatGPT they are displayed only as “Passkey.”
On the Daybreak setup page, I still see:
“To continue, add a hardware key. For your second sign-in method, you can use another security key or a passkey.”
The Continue button remains disabled.
I removed all software/synced passkeys, including Windows Hello, Bitwarden, and Google Password Manager. Only the two physical TrustKey T110 keys remain registered.
I also signed out, signed back in, and waited more than 15 minutes, but the Daybreak status did not change.
TrustKey has now publicly acknowledged that they reproduced the same issue with T110, where FIDO2 registration succeeds but OpenAI displays the credential as a Passkey instead of a physical Security Key.
Has anyone else experienced this with TrustKey or other non-YubiKey FIDO2 hardware keys? Did it eventually resolve, or was a backend/account-side fix required?
I can reproduce the exact same issue with a TrustKey T120 USB-C.
I tested enrollment both on:
iPhone / iOS via Safari and Chrome
Windows 11 via desktop browser
In both cases I explicitly selected Security key. The TrustKey T120 is detected correctly, I am prompted for the FIDO2 PIN, and I have to physically touch the hardware key to complete enrollment.
OpenAI then sends the “New security key or passkey added” confirmation email, but the credential is shown in ChatGPT only as “Passkey”.
The Daybreak page still says: “To continue, add a hardware key.”
So this appears to affect the TrustKey T120 as well as the T110. I have also opened a support ticket with OpenAI.
I have two separate TrustKey T110 physical FIDO2 security keys registered on my OpenAI account. They are the only passkeys/security keys registered.
During registration, Windows Security explicitly states that the credential will be saved to the security key, asks for the hardware-key PIN, and requires physical touch, so these are not software or synced passkeys.
Advanced Account Security is enabled, but Daybreak still tells me that I need to add a hardware security key.
I’ve raised this with OpenAI Support. They have confirmed that keys supplied through the OpenAI/Yubico bundle are supported for Daybreak, but so far have not confirmed whether the T110 itself is considered incompatible or whether this is an account/credential-recognition problem.
Support also told me that physical hardware keys must be the only registered login methods and that software/synced passkeys are not eligible. In my case that condition is already satisfied, so it does not explain the failure.
Hopefully adding another reproducible case helps get this looked at as a Daybreak key-recognition issue rather than individual setup error.
I can reproduce the same issue with a TrustKey T120 USB-C on both:
Windows 11
macOS
On both platforms I explicitly selected the external/security-key flow. The T120 requires its FIDO2 PIN and physical touch, registration succeeds, but OpenAI still displays the resulting credential only as “Passkey” and Daybreak continues to say:
“To continue, add a hardware key.”
I also queried the key directly over CTAP2 on Windows:
AAGUID: e3512a8a-62ae-11ea-bc55-0242ac130003
VID/PID: 311f:a6e9
Transport: usb
Versions: U2F_V2, FIDO_2_0, FIDO_2_1_PRE
plat: false
rk: true
clientPin: true
up: true
Attestation: packed
Firmware: v213.11.139
So the authenticator is clearly presenting as an external roaming FIDO2 hardware key, not a platform/synced passkey.
I also removed all software passkeys and reproduced this in private/incognito sessions. The behavior is unchanged.
I’ve opened a support case with OpenAI as well. At this point this looks like a Daybreak-side hardware-key recognition / AAGUID / attestation-classification issue rather than a local setup problem.
OpenAI support initially suggested that the active ChatGPT/account incident might be affecting how Daybreak classifies newly added security keys.
After the incident was marked resolved, I removed the previously registered credential and enrolled my TrustKey T120 again on iPhone/iOS.
The result is unchanged: enrollment completes successfully with the FIDO2 PIN + physical touch, but OpenAI still lists the key as “Passkey”, Daybreak still says “To continue, add a hardware key”, and the Continue button remains disabled.
I reported the result back to OpenAI support and the case has now been escalated to a support specialist.
I’ll update the thread if I receive a definitive answer about TrustKey compatibility or the hardware-key classification issue.
